Activity log for bug #1382510

Date Who What changed Old value New value Message
2014-10-17 10:57:31 Grzegorz Gutowski bug added bug
2014-10-17 11:17:44 Martin Pitt nominated for series Ubuntu Trusty
2014-10-17 11:17:44 Martin Pitt bug task added systemd (Ubuntu Trusty)
2014-10-17 11:19:26 Martin Pitt systemd (Ubuntu): status New Fix Released
2014-10-17 11:19:37 Martin Pitt systemd (Ubuntu Trusty): status New Triaged
2014-10-17 11:19:40 Martin Pitt systemd (Ubuntu Trusty): importance Undecided High
2014-10-17 11:19:43 Martin Pitt systemd (Ubuntu Trusty): assignee Martin Pitt (pitti)
2014-10-17 11:19:50 Martin Pitt systemd (Ubuntu Trusty): milestone ubuntu-14.04.2
2014-10-17 11:23:00 Martin Pitt summary systemd-logind upstart script is flawed systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch
2014-10-29 07:01:01 Martin Pitt description /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so &> /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) My system info: # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 /etc/init/systemd-logind.conf contains the following:     # only start if PAM module is actually available, not if libpam-systemd is     # removed but not purged     [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so &> /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) SRU TEST CASE ============= - On an amd64 system, run "sudo apt-get install libpam-systemd:i386" - Then run "sudo restart systemd-logind" - On current trusty this will result in stop/waiting, with the error in /var/log/upstart/systemd-logind.log as above. - With this fix this will result in start/running and no error. My system info: # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy libpam-systemd libpam-systemd:   Installed: 204-5ubuntu20.7   Candidate: 204-5ubuntu20.7
2014-10-29 07:06:47 Martin Pitt bug added subscriber Ubuntu Stable Release Updates Team
2014-10-29 07:06:53 Martin Pitt systemd (Ubuntu Trusty): status Triaged In Progress
2014-10-30 20:25:28 Brian Murray systemd (Ubuntu Trusty): status In Progress Fix Committed
2014-10-30 20:25:32 Brian Murray bug added subscriber SRU Verification
2014-10-30 20:25:36 Brian Murray tags verification-needed
2014-10-31 01:02:50 Mathew Hodson tags verification-needed verification-done
2014-11-13 07:43:35 Launchpad Janitor systemd (Ubuntu Trusty): status Fix Committed Fix Released