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. ;-)
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
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 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. Thanks, Leen, I'm sending you the log direct (zipped). Carl -- 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