Bug#717403: [Pkg-systemd-maintainers] Bug#717403: libpam-systemd fails when talking to old systemd-logind service

2013-07-24 Thread Michael Biebl
clone 717403 -1 retitle -1 libpam-systemd: no login when PAM_SESSION_ERR is triggered thanks Am 20.07.2013 14:20, schrieb Michael Biebl: Jul 20 14:08:08 pluto login[3476]: pam_unix(login:session): session opened for user michael by LOGIN(uid=0) Jul 20 14:08:08 pluto systemd-logind[5664]: New

Bug#717403: [Pkg-systemd-maintainers] Bug#717403: libpam-systemd fails when talking to old systemd-logind service

2013-07-21 Thread Michael Stapelberg
Hi Michael, Michael Biebl bi...@debian.org writes: Jul 20 14:08:08 pluto login[3476]: pam_systemd(login:session): Failed to parse message: Message has only 5 arguments, but more were expected […] 2/ The above looks like a D-Bus API break in the logind API and we should probably notify

Bug#717403: libpam-systemd fails when talking to old systemd-logind service

2013-07-20 Thread Michael Biebl
Package: libpam-systemd Version: 204-1 Severity: important We currently do not restart systemd-logind as part of the upgrade process. That means, when you try to login after the upgrade, libpam-systemd will talk to the old logind (v44) process. I get the following in the journal: Jul 20