Version: (using KDE KDE 3.5.2) Installed from: Gentoo Packages Compiler: gcc-3.4.5 OS: Linux I enabled the auto login with locking the screen. When I change to the console while the auto login countdown is running, the locking of the screen fails! Changing back to X, lets me use KDE w/o a need of a password... Also tested on debian/etch with kde 3.5.1.
The KDM auto login situation is acutally getting worse: - pressing Escape doesn't cancel the auto login any more - pressing Tab cancels the autologin - but just for let's say 15secs - the lock-on-auto-login feature is still useless, due to the bug described above. KDE 3.5.5 - gentoo as well as debian/etch If this is not fixable - I suggest removing the feature completely, it just pretends some security which hardly exists.
*** Bug 141540 has been marked as a duplicate of this bug. ***
confirmed. the key is most probably this: kdesktop: WARNING: LockProcess::startSaver() grabInput() failed!!!! as a "special feature", the session does not accept keyboard input (the x server's alt-ctrl-combos still work, though). lubos? re comment #1: the situation is not getting worse, but new features are added. if you don't want the persisting auto-login, turn it off. it's off by default, btw. ;)
btw, the "keyboard gone" problem seems to be unrelated to the locking failure, but clearly has the same trigger - see bug #143343.
*** Bug 143343 has been marked as a duplicate of this bug. ***
Either X or KDM bug, depending on how much KDM does. Neither keyboard nor locking works because something has keyboard grab or at least X thinks so (running a testapp which tries to call XGrabKeyboard() returns AlreadyGrabbed). Grepping in KDM sources show some XGrabKeyboard() calls but no matching XUnrabKeyboard() calls, so I suggest you check that and either fix it, otherwise this is X bug and nothing we could do about it.
well, the greeter simply terminates - that should release any grabs it holds, no? also, this wouldn't explain why it happens only when the display isn't on the current vt.
closing as invalid, as this isn't kde's fault after all. i reported this to xorg at http://bugs.freedesktop.org/show_bug.cgi?id=13675 , but now i can't reproduce it myself any more, so it must have been fixed meanwhile. comment there if you have something substantial to add.
Thanks for looking at it - and sorry for blaming the wrong guys ;) Happy Christmas!