[Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

2016-04-22 Thread Steve Langasek
It is longstanding practice, predating either upstart or systemd, that users of Debian and Ubuntu systems should create a /usr/sbin/policy-rc.d as part of their chroot setup. It is not a bug in the libpam-systemd package that it tries to start and stop its service using the policy- declared

[Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

2016-04-12 Thread Dustin Kirkland 
I am reopening the Trusty task, as I've re-confirmed this bug in 14.04 chroot. apt upgrading will fail on libpam-systemd: root@x250:/# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following

[Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

2015-10-28 Thread Rob Brew
** Changed in: systemd (Ubuntu Trusty) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1325142 Title: failure to update libpam-systemd in

[Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

2014-08-04 Thread Martin Pitt
This is fixed in utopic, as the init script went away completely, in favor of always using D-BUS activation. ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Utopic) Importance: High Status: Confirmed ** Changed in: