When using kdm, logging out from a session with the current git x server returns to the kdm login screen as expected - but it doesn't take any keyboard or mouse input. Checking /var/log/Xorg.0.log shows these new entries after returning to kdm: (II) UnloadModule: "kbd" (II) UnloadModule: "mouse" (II) Open ACPI successful (/var/run/acpid.socket) (II) APM registered successfully (II) RADEONHD(0): Mapped IO at 0xb7f07000 (size 0x00010000) (II) RADEONHD(0): Mapped FB at 0xa7e4d000 (size 0x10000000) (II) RADEONHD(0): Using 2383 scanlines of offscreen memory (II) RADEONHD(0): RandR 1.2 enabled, ignore the following RandR disabled message. (II) RADEONHD(0): Using HW cursor (**) RADEONHD(0): DPMS enabled (--) RandR disabled (II) AIGLX: Screen 0 is not DRI2 capable (II) AIGLX: Screen 0 is not DRI capable (II) GLX: Initialized MESA-PROXY GL provider for screen 0 (II) RADEONHD(0): Setting screen physical size to 376 x 301 (EE) Error loading keymap /var/lib/xkb/server-0.xkm (EE) Error loading keymap /var/lib/xkb/server-0.xkm The problem quite clearly appears to be the first 2 lines -- the keyboard and mouse drivers are both being unloaded (for no obvious reason) and not reloaded. The X server is compiled without HAL support, and the keyboard/mouse settings are hardcoded in xorg.conf as Section "ServerLayout" [...] InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "on" Option "Protocol" "ExplorerPS/2" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "de" Option "XkbModel" "pc105" Option "XkbVariant" "nodeadkeys" EndSection
(In reply to comment #0) > When using kdm, logging out from a session with the current git x server > returns to the kdm login screen as expected - but it doesn't take any keyboard > or mouse input. > Can you try reverting 6d22a9615a0e6ab3d00b0bcb22ff001b6ece02ae?
Reverting 6d22a9615a0e6ab3d00b0bcb22ff001b6ece02ae fixes it. So does simply reverting the CloseDevice -> DeleteInputDeviceRequest change from 6d22a9615a0e6ab3d00b0bcb22ff001b6ece02ae
This bug is entwined with the original fix to 14418, so I'll mark it as a duplicate. See comment 14 to #14418. https://bugs.freedesktop.org/show_bug.cgi?id=14418#c14 *** This bug has been marked as a duplicate of bug 14418 ***
Fixes pushed as 9ab4e2fd8eaa87dbd16835affb1aa54dcb1a619e aec485f2dcc87b340759d67b60e7dee7931aaec5 and f377141912594f87144d6d7f7fdd279a101d8e6c See bug 14418.
Removing duplicate status, there are two parts to the bug and the part this bug describes has been fixed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.