Comment 40 for bug 1325142

Can you explain how you can fuck up an LTS release upgrade (not even a major upgrade)? If you just had *one* test system running, you would have been able to reproduce this. Amateurs...

apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libpam-systemd
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
19 not fully installed or removed.
Need to get 0 B/25.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 424067 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_204-5ubuntu20.11_amd64.deb ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart-session/1001/2593: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: warning: subprocess old pre-removal script returned error exit status 100
dpkg: trying script from the new package instead ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart-session/1001/2593: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing archive /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.11_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 100
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart-session/1001/2593: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.11_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)