[SLE] 32-bit 10.1 post-screensaver keyboard / mouse problems?
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. It happened again the next time the screensaver was activated. This time I lost the mouse *and*... progressively... the keyboard. It seemed as though I had just enough keystrokes remaining to close KMail but it then rapidly lost function. At that point I was 'frozen' at the desktop with no working mouse or keyboard. I ssh'd in from another system, logged as root and repeated the 'init 3' - 'init 5' sequence. I was able to log back into my desktop and the keyboard and mouse were working again. I shut down and booted into 10.0 to get some work done and haven't had a problem since. 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? TIA & regards, 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
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
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
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
On Friday 09 June 2006 19:59, Carl Hartung wrote:
Hi All,
Has anybody else had a mouse/keyboard get locked after the screensaver has been activated and deactivated?
Yep, Happens to me quite regularly. I just shrug my shoulders and carry on. I clear it by quitting X and logging in again. Bob S. PS This is in 10.0 HDE 3.5.2 -- 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
On Sunday 11 June 2006 05:10, Bob S wrote:
On Friday 09 June 2006 19:59, Carl Hartung wrote:
Hi All,
Has anybody else had a mouse/keyboard get locked after the screensaver has been activated and deactivated?
Yep,
Happens to me quite regularly.
I just shrug my shoulders and carry on. I clear it by quitting X and logging in again.
Bob S.
PS This is in 10.0 HDE 3.5.2
Interesting. Another 10.0/3.5.2 combo. Anybody who /had/ this problem, but not anymore because they upgraded KDE to 3.5.3? 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
On Sunday 11 June 2006 03:31, Leendert Meyer wrote:
On Sunday 11 June 2006 05:10, Bob S wrote:
On Friday 09 June 2006 19:59, Carl Hartung wrote:
Hi All,
Has anybody else had a mouse/keyboard get locked after the screensaver has been activated and deactivated?
Yep,
Happens to me quite regularly.
I just shrug my shoulders and carry on. I clear it by quitting X and logging in again.
Bob S.
PS This is in 10.0 HDE 3.5.2
Interesting. Another 10.0/3.5.2 combo. Anybody who /had/ this problem, but not anymore because they upgraded KDE to 3.5.3?
Thanks Leen & Bob! More info on the problem follows and I appreciate any additional input. regards, Carl The screensaver/keyboard-mouse problem is with KDE 3.5.2 level 'a' on 10.1. KDE 3.5.2 level 'a' on 9.3 on the same system doesn't exhibit this problem; ditto 'stock' GNOME 2.12 on 10.0. Other issues on this system running 10.1 (note: all the error messages come from /var/log/messages. I'm still looking at a series of .xsession-errors 'snapshots'): * package management / updater stack error messages: (see 'Addendum A' below for details) * Konqueror segfaults at least a few times each session when I'm browsing the filesystem and I right-click on an icon. No context-sensitive menu displays... not enough time. Right-clicking on the icon causes Konqueror to immediately close and the crash handler to pop up. * /var/log/messages warnings/errors unique to 10.1: "kernel: Driver 'sd' needs updating - please use bus_type methods" and "hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hdb: task_no_data_intr: error=0x04 { DriveStatusError } ide: failed opcode was: 0xef" (see 'Addendum B' below for details) and "linux gconfd (carl10-1-3633): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-carl10-1/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)" and -start- linux gconfd (carl10-1-3515): Resolved address "xml::/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 0 linux gconfd (carl10-1-3515): None of the resolved addresses are writable; saving configuration settings will not be possible linux gconfd (carl10-1-3515): Resolved address "xml::/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 linux gconfd (carl10-1-3515): None of the resolved addresses are writable; saving configuration settings will not be possible -end- and "linux hp: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 84" and -start- linux zmd: NetworkManagerModule (WARN): Failed to connect to NetworkManager linux zmd: Daemon (WARN): Not starting remote web server linux syslog-ng[2058]: STATS: dropped 0 linux checkproc: checkproc: Empty pid file /var/lock/susehelpindex for /usr/bin/susehelpindex linux syslog-ng[2058]: SIGHUP received, restarting syslog-ng linux syslog-ng[2058]: new configuration initialized -end- = = = = = = Addendum A = = = = = = Note: I am 'on the sidelines' waiting for mirrors to sync and more feedback to appear on SLE before applying the latest (or "official") 'updater' patches. I'm sharing these error messages because they exist and may be related to some of the other problems(?): linux suse_register[3679]: Commandline params: no-optional:0 forceregistration:0 no-hw-data:0 list-params:1 forcezmdconfig:0 interactive:0 browser: linux suse_register[3679]: Argument Dump: $VAR1 = { 'timezone' => 'US/Eastern', 'processor' => 'athlon', 'platform' => 'i386' }; linux suse_register[3679]: Products Dump: $VAR1 = []; linux suse_register[3679]: No products to register (100) linux suse_register[3713]: Installed Products Dump: $VAR1 = [ [ 'SUSE-Linux-10.1-Add-on', '10.1', '0', 'i686' ] ]; linux suse_register[3713]: Commandline params: no-optional:0 forceregistration:0 no-hw-data:0 list-params:0 forcezmdconfig:0 interactive:0 browser: linux suse_register[3713]: Argument Dump: $VAR1 = { 'timezone' => 'US/Eastern', 'processor' => 'athlon', 'platform' => 'i386' }; linux suse_register[3713]: Products Dump: $VAR1 = []; linux suse_register[3713]: No products to register (100) linux su: (to root) carl10-1 on /dev/pts/2 linux su: (to root) carl10-1 on /dev/pts/2 linux syslog-ng[2535]: STATS: dropped 0 linux suse_register[3911]: Installed Products Dump: $VAR1 = [ [ 'SUSE-Linux-10.1-Add-on', '10.1', '0', 'i686' ] ]; linux suse_register[3911]: Commandline params: no-optional:0 forceregistration:1 no-hw-data:0 list-params:0 forcezmdconfig:0 interactive:0 browser: linux suse_register[3911]: Argument Dump: $VAR1 = { 'timezone' => 'US/Eastern', 'processor' => 'athlon', 'platform' => 'i386' }; linux suse_register[3911]: Products Dump: $VAR1 = []; linux suse_register[3911]: No products to register (100) linux suse_register[3943]: Installed Products Dump: $VAR1 = [ [ 'SUSE-Linux-10.1-Add-on', '10.1', '0', 'i686' ] ]; linux suse_register[3943]: Commandline params: no-optional:0 forceregistration:0 no-hw-data:0 list-params:0 forcezmdconfig:0 interactive:0 browser: linux suse_register[3943]: Argument Dump: $VAR1 = { 'timezone' => 'US/Eastern', 'processor' => 'athlon', 'platform' => 'i386' }; linux suse_register[3943]: Products Dump: $VAR1 = []; linux suse_register[3943]: No products to register (100) also: linux zmd: NetworkManagerModule (WARN): Failed to connect to NetworkManager linux zmd: Daemon (WARN): Not starting remote web server = = = = = = Addendum B = = = = = = Partitions: /dev/hdb7 9.3 '/' /dev/hdb8 10.0 '/' /dev/hdb9 /home (with ~/carl93, ~carlh & ~/carl10-1 user directories) /dev/hdb10 10.1 '/' There are no comparable ide or hdb error messages at all under 9.3 or 10.0. There are no comparable 'bad behavior' (i.e. "serious") problems under 9.3 or 10.0, either. 'reiserfsck --fix-fixable' on '/' for 10.1 yielded no actual filesystem problems or corruptions: reiserfsck --fix-fixable started at Sun Jun 11 08:59:13 2006 ########### Replaying journal.. Reiserfs journal '/dev/hdb10' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 81886 Internal nodes 553 Directories 25847 Other files 320383 Data block pointers 1888003 (1660 of them are zero) Safe links 0 ########### reiserfsck finished at Sun Jun 11 09:09:36 2006 -- 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
participants (3)
-
Bob S
-
Carl Hartung
-
Leendert Meyer