Bug#337234: xorg-x11: x stops receiving keyboard events after xscreensaver started
Hi, On Thu, Nov 03, 2005 at 02:58:04PM +0100, Michel Dänzer wrote: On Thu, 2005-11-03 at 13:28 +, Paul Brossier wrote: after xscreensaver starts, if i try to type in my password to unlock the screen, no * is printed, and the timer gets reseted to the beginning. first of all, this xscreensaver behaviour is a feature, not a bug: the new xscreensaver just doesn't show the * anymore, and it makes sense to reset the timer on key presses. i still loose the keyboard though. if i go to console mode with alt+ctl+f1, and kill xscreensaver, the mouse works fine, and alt+tab too. but no other key event seem to be able to reach the screen. some other weird things happen, such as the gnome menu not willing to open. i tried killing just about all my processes from the console, but no luck. restarting X does it. the keyboard is an apple usb keyboard with an italian layout (but i prefer the us one). Does this always happen, i.e. has it happened several times? There's a known issue (that unfortunately still hasn't been tracked down, but most evidence points towards the kernel) where sometimes a key gets 'stuck', and if that happens to be a modifier, it can cause symptoms such as those you describe. not every times, but it just happened again, and when xscreensaver was not locked. i could see the mouse for a while after the screen woke up, then lost everything, even alt+tab. i then moved to console and killed xscreensaver. X segfaulted again then (i attach the Xorg.0.log, which is very similar to the one i sent already). Another possibility would be that a client is keeping the keyboard grabbed, although that's rather unlikely given that you killed 'just about all' your processes and that alt-tab still works. Nonetheless, you may want to read up on Option AllowDeactivateGrabs in the xorg.conf(5x) manpage and see if that helps. Option AllowDeactivateGrabs boolean This option enables the use of the Ctrl+Alt+Keypad-Divide key sequence to deactivate any active keyboard and mouse grabs. Default: off. indeed, looks like it could help me getting the keys back. i will see if that helps. cheers, piem $ tail -n 100 /var/log/Xorg.0.log.old (**) Generic Keyboard: Protocol: standard (**) Option AutoRepeat 500 30 (**) Option XkbRules xorg (**) Generic Keyboard: XkbRules: xorg (**) Option XkbModel macintosh (**) Generic Keyboard: XkbModel: macintosh (**) Option XkbLayout us (**) Generic Keyboard: XkbLayout: us (**) Option CustomKeycodes off (**) Generic Keyboard: CustomKeycodes disabled (**) Option Protocol ImPS/2 (**) Configured Mouse: Device: /dev/input/mice (**) Configured Mouse: Protocol: ImPS/2 (**) Option CorePointer (**) Configured Mouse: Core Pointer (**) Option Device /dev/input/mice (**) Option Emulate3Buttons true (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Configured Mouse: ZAxisMapping: buttons 4 and 5 (**) Configured Mouse: Buttons: 5 (II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE) (II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD) (II) Configured Mouse: ps2EnableDataReporting: succeeded Warning: font renderer for .pcf already registered at priority 0 Warning: font renderer for .pcf.Z already registered at priority 0 Warning: font renderer for .pcf.gz already registered at priority 0 Warning: font renderer for .snf already registered at priority 0 Warning: font renderer for .snf.Z already registered at priority 0 Warning: font renderer for .snf.gz already registered at priority 0 Warning: font renderer for .bdf already registered at priority 0 Warning: font renderer for .bdf.Z already registered at priority 0 Warning: font renderer for .bdf.gz already registered at priority 0 Warning: font renderer for .pmf already registered at priority 0 Could not init font path element unix/:7100, removing from list! (WW) Open ACPI failed (/proc/acpi/event) (No such file or directory) (II) No APM support in BIOS or kernel (II) Configured Mouse: ps2EnableDataReporting: succeeded (WW) Open ACPI failed (/proc/acpi/event) (No such file or directory) (II) No APM support in BIOS or kernel (II) Configured Mouse: ps2EnableDataReporting: succeeded SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled (WW) Open ACPI failed (/proc/acpi/event) (No such file or directory) (II) No
Bug#337234: xorg-x11: x stops receiving keyboard events after xscreensaver started
Package: xorg-x11 Severity: important Hi. i just installed the 6.8.99.901.dfsg.1-1 packages built by Sven Luther for powerpc, that are now reaching experimental. after xscreensaver starts, if i try to type in my password to unlock the screen, no * is printed, and the timer gets reseted to the beginning. if i go to console mode with alt+ctl+f1, and kill xscreensaver, the mouse works fine, and alt+tab too. but no other key event seem to be able to reach the screen. some other weird things happen, such as the gnome menu not willing to open. i tried killing just about all my processes from the console, but no luck. restarting X does it. the keyboard is an apple usb keyboard with an italian layout (but i prefer the us one). the relevant section in my xorg.conf reads: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us Option XkbOptionslv3:lwin_switch EndSection cheers, piem -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-powerpc64 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337234: xorg-x11: x stops receiving keyboard events after xscreensaver started
On Thu, 2005-11-03 at 13:28 +, Paul Brossier wrote: after xscreensaver starts, if i try to type in my password to unlock the screen, no * is printed, and the timer gets reseted to the beginning. if i go to console mode with alt+ctl+f1, and kill xscreensaver, the mouse works fine, and alt+tab too. but no other key event seem to be able to reach the screen. some other weird things happen, such as the gnome menu not willing to open. i tried killing just about all my processes from the console, but no luck. restarting X does it. the keyboard is an apple usb keyboard with an italian layout (but i prefer the us one). Does this always happen, i.e. has it happened several times? There's a known issue (that unfortunately still hasn't been tracked down, but most evidence points towards the kernel) where sometimes a key gets 'stuck', and if that happens to be a modifier, it can cause symptoms such as those you describe. Another possibility would be that a client is keeping the keyboard grabbed, although that's rather unlikely given that you killed 'just about all' your processes and that alt-tab still works. Nonetheless, you may want to read up on Option AllowDeactivateGrabs in the xorg.conf(5x) manpage and see if that helps. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#337234: xorg-x11: x stops receiving keyboard events after xscreensaver started
Version: 6.8.99.901.dfsg.1-1 more info about this. i just killed xscreenserver from the console again, except this time x crashed. the line 'SetGrabKeysState - disabled' appears when the screensaver starts. cheers, piem $ tail -n 50 /var/log/Xorg.0.log.old (II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE) (II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD) (II) Configured Mouse: ps2EnableDataReporting: succeeded Warning: font renderer for .pcf already registered at priority 0 Warning: font renderer for .pcf.Z already registered at priority 0 Warning: font renderer for .pcf.gz already registered at priority 0 Warning: font renderer for .snf already registered at priority 0 Warning: font renderer for .snf.Z already registered at priority 0 Warning: font renderer for .snf.gz already registered at priority 0 Warning: font renderer for .bdf already registered at priority 0 Warning: font renderer for .bdf.Z already registered at priority 0 Warning: font renderer for .bdf.gz already registered at priority 0 Warning: font renderer for .pmf already registered at priority 0 Could not init font path element unix/:7100, removing from list! (WW) Open ACPI failed (/proc/acpi/event) (No such file or directory) (II) No APM support in BIOS or kernel (II) Configured Mouse: ps2EnableDataReporting: succeeded SetGrabKeysState - disabled (WW) Open ACPI failed (/proc/acpi/event) (No such file or directory) (II) No APM support in BIOS or kernel (II) Configured Mouse: ps2EnableDataReporting: succeeded *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0xa0) [0x10045ff0] 1: [0x1002f4] 2: [(nil)] 3: /usr/X11R6/bin/X [0x1009e498] 4: /usr/X11R6/bin/X [0x1009e674] 5: /usr/X11R6/bin/X [0x1009e910] 6: /usr/X11R6/bin/X(CoreProcessPointerEvent+0x4e8) [0x1009f7f8] 7: /usr/X11R6/bin/X(ProcessPointerEvent+0x90) [0x10118330] 8: /usr/X11R6/bin/X(xf86eqProcessInputEvents+0x298) [0x10053c48] 9: /usr/X11R6/bin/X(ProcessInputEvents+0x24) [0x10044cf4] 10: /usr/X11R6/bin/X(Dispatch+0xd4) [0x10094f64] 11: /usr/X11R6/bin/X(main+0x484) [0x100a5f24] 12: /lib/tls/libc.so.6 [0xfd5382c] 13: /lib/tls/libc.so.6 [0xfd53974] Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
