Red Hat Bugzilla – Bug 476859
KDE screensaver hangs up after desktop gets locked
Last modified: 2009-02-04 08:26:34 EST
Description of problem:
I did a fresh install of F10 via the network, selected only KDE on my ThinkPad X200 laptop. I configured some power saving modes to auto-start screensaver (and lock it) and also suspend the display after some time of inactivity.
When the screen gets locked, I start typing in my password to unlock it but keyboard freezes then. I can use the mouse but can't click on any of the buttons (Switch User, Unlock, Cancel). No keyboard input works, so I can't get rid of X, can't switch to a console, etc.
I can remotely log into the laptop. Killing kblankscreen.kss, etc., doesn't help.
After this happens, the display stays lit and the screensaver doesn't kick in any more.
Version-Release number of selected component (if applicable):
Uses the fedora-updates repo, so KDE 4.1.3
rpm -q dbus kdebase-workspace
If not at dbus-1.2.4-2, please try updating to see if that helps (may require a reboot),
$ rpm -q dbus kdebase-workspace
Please update to dbus-1.2.4-2, and let us know if that helps or not.
You mean downgrade to dbus-1.2.4?
In the meantime, someone pointed out that compiz and the intel X video driver don't play well and that this is a known bug (I can't find the reference). I've disabled desktop effects and the system seems to work fine. I'll note here if I can provide new information.
dbus-1.2.4-2 has Epoch: 1 and thus this is an upgrade to a higher EVR. It was reverted because of the high amount of breakage the 1.2.6 and 1.2.8 versions caused.
[ltinkl@localhost ~]$ rpm -q dbus kdebase-workspace
I have the above and both locking and unlocking works correctly for me
Reporter, have you tried this recently and is it working?
I think it was the desktop effects. After disabling, I've not had any problems.