On Saturday 10 June 2006 01:59, Carl Hartung wrote:
Hi All,
Has anybody else had a mouse/keyboard get locked after the screensaver has been activated and deactivated?
I returned to my system last night after an hour or two with the screensaver running. I moved my mouse and my KDE desktop reappeared, sans pointer. It wasn't a case where the pointer was invisible, as no motion in any direction caused the focus to shift on the desktop. Likewise, randomly clicking and right-clicking the mouse buttons yielded nothing.
I navigated between virtual desktops and running programs using the keyboard to close everything down in an orderly fashion. I then switched to tty1 (Ctl+Alt+F1) logged in as root, ran 'init 3' then 'init 5' and logged back in. Both the keyboard and mouse were working again. ... In case it matters: The keyboard is 'vanilla' PS2 and the mouse USB with scroll wheel (no problems from 9.0 through 10.0)
Troubleshooting ideas and/or similar problems, anyone?
1. You did not mention if you checked the logs. Probably nothing in /var/log/{messages,warn}, but how about ~/.xsession-errors? 2. Did this "feature" happen after you updated KDE-3.5.3 to the one containing the screensaver fix? 3. I have always a System Monitor applet sitting in my taskbar, so that I can easily see if my CPU is at 100%. A few days ago I had an issue with setting up my screen saver (celtic). Celtic was going crazy (only in the screensaver setup dialog), the mouse did barely move and the keyboard was almost unresponsive, and my CPU was running at 100% (visible in the System Monitor applet). [Hmm, this reminds me of filing a bug report...]. Point is: how is your CPU doing if this "feature" manifests itself? Running at 100%? 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