reopen 550042 = severity 550042 important thanks In the proposed fix for this bug, the Xsession.d item was replaced by an xdg autostart item. So xscreensaver still starts automatically for every desktop session.
In a KDE session, this causes a conflict between xscreensaver and KDE's own screen saver service. The xscreensaver daemon should not be launched during a KDE session. On my system, if a KDE session is left untouched for a while, the session locks in a way that makes it impossible to unlock: any keyboard or mouse activity brings up the xscreensaver unlock dialogue, and even the correct password is rejected. Unless it is possible to log in remotely and take some action as root, the system has become completely unusable. Therefore, I have upgraded the severity to "important", though perhaps it ought to be "grave". In my opinion, this package should not cause any automatic startup at all of the xscreensaver daemon. It is the responsibility of each desktop environment and window manager to decide what automatic screen saver services, if any, to provide by default. Thanks, Yitz -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
