![](https://seccdn.libravatar.org/avatar/eba995a98a959e1d4ae7b36a1ca31293.jpg?s=120&d=mm&r=g)
On Saturday 10 June 2006 03:52, Carl Hartung wrote:
On Friday 09 June 2006 20:53, Leendert Meyer wrote:
1. You did not mention if you checked the logs. Probably nothing in /var/log/{messages,warn}, but how about ~/.xsession-errors?
Hi Leen,
I didn't see anything I recognized in 'warn' or 'messages' or .xsession-errors but maybe another pair of eyeballs might help. ;-)
Couldn't find a clue either. But I'm not really an expert with that. ;P Hint: make a copy of ~/.xsession-errors after KDE has started up, and right before you let the screensaver kick in. That's the reference point, errors are expected to show up after that (I discovered an error on my system this way). And make a copy right before you kill the session (should contain the interesting stuff).
2. Did this "feature" happen after you updated KDE-3.5.3 to the one containing the screensaver fix?
I actually installed the 'stock' 10.1 and /immediately/ upgraded KDE to 3.5.2 level 'a' just before the supplementary branch was moved. This is the same version installed in my 'daily' 10.0 and my 'fallback' 9.3 on this system, so I wasn't planning on upgrading to 3.5.3
Hmm, upgrade to the latest 3.5.3 and see if the bug is still there. A bughunt is useless if the bug is known and fixed. ;)
3. I have always a System Monitor applet sitting in my taskbar, so that I can easily see if my CPU is at 100%.
The external login was 'snappy'... the init 3 / init 5 response times were
Snappy? That's not a sign that the CPU is going crazy.
both instantaneous. Of course, this was /after/ the screensaver was 'sleeping' again with the kb/mouse not functioning... I'll remember to run 'top' next time... from the other system, if needed.
Try to minimize the "circumstances": Does it happen with a newly created user? Does it happen on a clean desktop (no other apps running [evolution], might clear up .xsession-errors too)? IMO upgrade to the latest KDE is the /first/ you should do, and see if the bug is still there. Cheers, Leen -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com