> With XscreenSaver 5.10-3 we shipped xdg and the Xsession.d file wasn't > removed,
Yes, thanks. I did figure that out though. > please remove the Xsession.d and test. I did that. The problem still occurs. When I also remove xscreensaver-daemon.desktop, the problem is fixed. >> In my opinion, this package should not cause any >> automatic startup at all of the xscreensaver >> daemon. > So KDE will provide it only for kscreensaver No, KDE will not provide it at all. KDE runs xscreensaver hacks inside its own screen saver service. The xscreensaver daemon should never run in a KDE session. > and GNOME only gnome-screensaver. I don't know how GNOME's screen saver service works, but I suspect that also for GNOME it is a bug for xscreensaver daemon to run. It's not clear yet if that bug is so severe that the system freezes up in GNOME as it does in KDE, but it's still a bug. See #519061. > If someone is new and doesn't know how to set it up > automatic startup for xscreensaver it can't do it. Right? It depends what kind of environment they are using. In KDE and GNOME, the desktop manager will automatically set up whatever needs to be set up. In fact, they already do that - without us trying to force xscreensaver daemon down their throats. The same is true for any other environment that is designed for screen savers to work without configuration, each in its own way. In raw X with a minimalist window manager, such as xmonad or dwm or twm, it is definitely the user's responsibility to start xscreensaver daemon. That matches the "stay out of my way" philosophy of those environments, and it is clearly explained in their documentation. So it is also a bug to start xscreensaver daemon automatically in that type of environment. Someone who is "new and doesn't know how to set it up" - and doesn't want to learn how - should not be using xmonad and friends. There are many other window managers and desktop environments, each with its own philosophy. For some, perhaps it may be right for xscreensaver daemon to launch automatically. For many it is definitely very wrong. It is impossible for this package to do exactly the right thing for every environment every time. Just install xscreensaver, and let each environment decide for itself if and how it gets launched. > With the xdg.desktop it's suppossed you can deactivate > it on your window manager - startup manager. No, xdg autostart items are just that - they start automatically. If you put "crash_my_system.desktop" into that folder, the system will crash, and that is a serious bug. Similarly, if you put "works_for_gnome_but_crashes_kde.desktop" in there, it will do just that. The only things you can install into that folder are things that are guaranteed to work for *every* desktop environment. In this case, it breaks KDE, and I suspect that it also breaks GNOME. Some environments do have a "startup manager" UI to manage start-up items, but that doesn't give us permission to install broken things there. Actually, I think you have pointed out another possible issue. The X startup procedure for Debian should not launch the items in the xdg autostart folder unless an xdg-compliant desktop environment is being launched. For people who are only running a simple window manager and not running a desktop environment, these items should not be run. But in our case, that is irrelevant. xscreensaver daemon should *never* start automatically, unless a specific window manager or desktop environment calls for it. Thanks, Yitz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
