-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Sun, Dec 22, 2013 at 09:41:05AM +0100, Pascal Dormeau wrote: > On Sun, 22 Dec 2013 00:12:14 +0100 > Vincent Lefevre <[email protected]> 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. >
If libpam-systemd is not installed, no logind session is created at login, that's why you don't see the problem, I guess. If you could please check all the message in the very relevant bug #728361 it might also help debuging (in particular about the results of loginctl). Regards, - -- Yves-Alexis Perez -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQEcBAEBCgAGBQJStq9kAAoJEG3bU/KmdcClmegH/jL6tocOoJqp9cWCoWBxYRFV w4pmnKgcNqjqq8IiZRJ7d7q0zLmbHJQHRgy+s2pivzle7thtHsUepZ8XEdzAwJ/c sKTdItDhdpCTGwrRO42y8g3KM4ng4kazFK+XMezuBocHjcBh1HJh+s3h/54VUcuK Y1Gd2F9eU8nRTNy2TDw7j7J2YETzFWL9xRSj+yV7sDU3lub3r3GBohC33Un1XoaI WrAjHnL5HAhSlp202YH9k6PyNccYU547Wg/WtzH55Bc0PL1qFiDhkHErsqYpO4fQ EH1pq4m7qv2PbQ9++VdLyDDR/fwbUrKaMrioUvBFRW2Sozo2uT2o6ZG+r/qnNfQ= =Em87 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
