Mark Eichin wrote: > There are two issues here: > (1) according to apt-file search, gdmflexiserver is *only* provided > by gdm, not xdm (which I do happen to be running) nor kdm. (kdm > might provide something *like* it, but xscreensaver is hard > coded to have > *newLoginCommand: gdmflexiserver -l -a -c FLEXI_XSERVER > in the binary, so it wouldn't help if it did...) > (2) per debian policy, 7.2 "binary dependencies", xscreensaver needs > at *least* a "Suggests: gdm" to describe the above dependency... > > While it would be *better* to see the button go away if it can't > possibly work, I think you at least need to correct the packaging to > reflect the above.
Re 1) for kdm, the kdm-gdmcompat package provides a gdmflexiserver wrapper. Re 2) I have added Suggests: gdm | kdm-gdmcompat To address the original issue of removing the button when the session has not been started by gdm or kdm or there is no gdmflexiserver, I can suggest making a little wrapper that checks for this and sets the newLoginCommand property accordingly before launching the xscreensaver-daemon. For this I would like to know exactly how the xscreensaver-daemon is started in a XFCE session. Can somebody help me with this? Also, in sessions started by gdm the GDMSESSION environment variable is defined. Is there something similar for sessions started by kdm? Or xdm? Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
