This might be the answer to the lockups.
Uwe
-------------------------------------------------------------------------
Uwe Thiem Tel: +264 - 061 - 241223
P.O.Box 30955
Windhoek Email: [EMAIL PROTECTED]
Republic of Namibia [EMAIL PROTECTED]
http://www.kde.org
**********************************
You can still escape from the GATES of hell: Use KDE!
-------------------------------------------------------------------------
---------- Forwarded message ----------
Date: Tue, 25 Jan 2000 11:42:09 -0000
From: David Faure <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: Weird lockups (fwd)
Resent-Date: Tue, 25 Jan 2000 12:44:01 +0100
Resent-From: [EMAIL PROTECTED]
I've heard that krootwm could cause X server locks.
See the following newsgroup post.
Fortunately we dropped this and have a clean solution now (kdesktop).
David.
-----------------------
Subject:
Re: KDE is locked up - can't do anything: TEMPORARY SOLUTION
Date:
Thu, 20 Jan 2000 13:53:13 +0300
From:
Nikita V. Youshchenko <[EMAIL PROTECTED]>
Organization:
CS MSU
Newsgroups:
comp.windows.x.kde
References:
1 , 2 , 3
>> Kill the X server: Ctrl-Alt-Backspace
>>
>> That's a bit draconic, so you could also run through the ps output
looking
>> for things that start with 'k' running under your ID.
>
>A couple of times my KDE seemed to hang as well. Even Ctrl-Alt-Backspace
>did not work. However I was able to log in to my machine from another
>one, using telnet, and I found out that kwm was using all CPU-time
>available. Killing kwm also killed the X-server. Starting KDE again
>worked fine thereafter.
>
>The problem seems (but I am not sure) to be related to switching between
>the virtual desktops, I remapped the ctrl-arrows to do that, and so far
>the problem only occured when I was using these ctrl-arrows relatively
>fast.
Being somewhat tired of KDE 1.1.2 lockups, I wrote a LD_PRELOAD and dlopen()
stub to find out, what KDE component actually grabs X server and doesn't
ungrab
it.
I was quite surprised to know that is was krootwm ...
The code that is there seems to be quite clear and bug-free. But the fact is
that on X locks, krootwm calls XGrabServer() and doesn't call
XUngrabServer()...
A temporary solution for now is to log in remotely and kill krootwm. The
session will unlock. Then do Alt+F2 and restart krootwm.
A better solution may be to hack krootwm code and make it to stop root icon
selection operation and ungrab server anyway, say, in 15 seconds.
Good luck.
Nikita.
