Comment 46 for bug 1325142

Hi, also same here, as here #1326412

I can remove it with "dpkg -r --force-depends" but then the package management is broken. When I reinstall it, the same error comes out:

*****
# apt-get --reinstall install libpam-systemd
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  libpam-systemd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/25.3 kB of archives.
After this operation, 136 kB of additional disk space will be used.
Selecting previously unselected package libpam-systemd:i386.
(Reading database ... 176516 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_204-5ubuntu20.12_i386.deb ...
Unpacking libpam-systemd:i386 (204-5ubuntu20.12) ...
Processing triggers for ureadahead (0.100.0-16) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up libpam-systemd:i386 (204-5ubuntu20.12) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing package libpam-systemd:i386 (--configure):
 subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
 libpam-systemd:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)

*****

so, what do we do if a LTS fails to be updated?