On Sun, 22 Dec 2013 00:12:14 +0100 Vincent Lefevre <vinc...@vinc17.net> wrote:
> When I upgraded my second machine yesterday, I noticed that both > libpam-systemd and systemd had been installed, so that I thought > the bug was related to one of them. So, I did some tests to see > what minimal change triggered the problem, and it was not due to > libpam-systemd (which depends on systemd), but to systemd itself. > That's why I've reassigned the bug to systemd. Well that might be more tricky than that, here systemd is used as PID1 (thus logind running) and lightdm works as expected without libpam-systemd. Only installing libpam-systemd triggers the problem. Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
