Bug 161152 - kdm doesn't accept keyboard/mouse input after logout
Summary: kdm doesn't accept keyboard/mouse input after logout
Status: RESOLVED NOT A BUG
Alias: None
Product: kdm
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-22 14:35 UTC by Bernhard Rosenkraenzer
Modified: 2008-05-19 17:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Patch for xorg xserver to fix this (526 bytes, patch)
2008-04-22 14:51 UTC, Bernhard Rosenkraenzer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Rosenkraenzer 2008-04-22 14:35:18 UTC 
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.3.0 
OS:                Linux

With current git Xorg, kdm stops accepting keyboard/mouse input after a logout:

1. Bootup
2. kdm ---> keyboard/mouse work
3. KDE ---> keyboard/mouse work
4. Logout
5. kdm ---> keyboard/mouse don't do anything at all, even keyboard LEDs don't work
6. ssh in, run "killall kdm" (kdm is automatically restarted by init)
7. keyboard/mouse work again

This happens both on trunk and on current 3.5 branch.

I suspect this is actually an X bug, but only kdm seems to trigger it (xdm seems to work).
Comment 1 Bernhard Rosenkraenzer 2008-04-22 14:47:53 UTC 
Debugging some more, it definitely is an X bug -- xserver/dix/devices.c does DeleteInputDeviceRequest().
Comment 2 Bernhard Rosenkraenzer 2008-04-22 14:51:41 UTC 
Created attachment 24478 [details]
Patch for xorg xserver to fix this

The attached patch (applied to xserver) fixes it. No need to do anything from
the KDE side, just putting in the patch for ppl coming across this bug report
when running into the same issue.
Comment 3 Oswald Buddenhagen 2008-04-28 16:51:02 UTC 
ah, so the usual workaround TerminateServer=true would work here, too.
Comment 4 Bernhard Rosenkraenzer 2008-04-28 17:01:36 UTC 
Yes, fixing the server is just the nicer thing to do ;)