Package: lightdm Version: 1.2.2-4 Followup-For: Bug #639984 Dear Maintainer,
we were bitten by that in a real environment, too. And, Yves-Alexis, you were wrong when saying other login managers act equally. I agree that when the lightdm binary is started directly it should somehow be able to auto-detect if it runs in a nested environment or not. Nonetheless we were using the runlevel startup scripts to restart lightdm over a ssh connection which failed while other login managers (namely kdm) did not. That way you can restart remotely any display manager I know of without fiddling with the DISPLAY variable. Thats why I ask you to accept this bug and maybe change the init script accordingly in order to ignore the DISPLAY variable. If wanted, I can write up a small patch which makes the behaviour configurable via /etc/defaults/lightdm. With kind regards, Jens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org