KDE 3.5 Crashing
Nikola Lecic
nlecic at EUnet.yu
Mon Jun 18 17:43:32 UTC 2007
On Sat, 16 Jun 2007 20:45:57 +1000
Gemma Fletcher <slvhwke at optusnet.com.au> wrote:
> On Friday 15 June 2007 21:41, Matthias Apitz wrote:
> > El día Friday, June 15, 2007 a las 09:33:27PM +1000, Gemma Fletcher
> escribió:
>
> > Can you check if only X or KDE is frozen, or the system at all?
> > Try to connect from some other host on the network.
> > Try to do some RAM testing as well.
> >
> > matthias
>
> Ok my RAM is fine and dandy. I'm not sure how to check to see if
> only KDE is frozen. Once is freezes I can't do anything. Not even
> reset with ctrl-alt-del. And my keyboard usually goes dead
> <indicated by my numlock light turning off>
>
> Its just me - so I have no other host to connect from. I did notice
> something though that i forgot to mention- it usually only crashes if
> I am doing some internet related activity. <Ie.Browsing, checking
> email, IM'ing etc> If I just do normal stuff like spreadsheeting, or
> developing or whatever it seems to run fine.
Hello Gemma,
Although it really looks like hardware, you can also do this to be 100%
sure it isn't software related:
(1) Had you used that computer before you have installed FreeBSD? It
would be a nice idea to post here the output of your 'dmesg'
or /var/log/messages.
(2) Have you tried to run a small script as Matthias proposed?
(3) Are you sure your ports are up-to-date? If in doubt, install
ports-mgmt/portupgrade and run
# portversion -v -L =
(4) If yes, as of "how to check X without KDE", do the following:
(a) run 'xinit' without ~/.xinitrc file to avoid starting KDE and
or any other window manager; (once you start it, you can go back
by 'exit' or Ctrl+Alt+Backspace; please note that you must put the
mouse over the window in order to move focus on it);
(b) check if there are warning -- (WW) -- or other suspicious messages
in /var/log/Xorg.0.log;
(c) while in pure xinit session, run Firefox or other application that
is not KDE/Qt related;
(d) run Opera, Skype or similar app that is Qt- but not KDE-related;
(e) run KDE applications (Konqueror, KMail, etc.)
and report one by one what happened, from (1) to (4e). Maybe it helps
to isolate the problem, besides hardware tests :)
Nikola Lečić
More information about the freebsd-questions
mailing list