On Sun, Nov 8, 2009 at 7:59 AM, Yitzchak Gale <g...@sefer.org> wrote: > 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.
With XscreenSaver 5.10-3 we shipped xdg and the Xsession.d file wasn't removed, please remove the Xsession.d and test. This bug (shipping both files) is going to be fixed on next upload. > > 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. So KDE will provide it only for kscreensaver and GNOME only gnome-screensaver. If someone is new and doesn't know how to set it up automatic startup for xscreensaver it can't do it. Right? Sorry but I don't think so. With the xdg.desktop it's suppossed you can deactivate it on your window manager - startup manager. Regards. -- Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118 0x7C4DF50D http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
