Comment 23 for bug 1295521

> I had both libpam-systemd:i386 and libpam-systemd:amd64
> on my AMD64 system and this confused PAM.

That makes no sense at all. PAM does not get confused by having the module available for multiple architectures. The amd64 libpam doesn't even *know* that the i386 pam module is installed, because these modules are (sensibly) each installed in architecture-specific paths which are invisible to one another.

I don't believe that having libpam-systemd:i386 installed on your system had anything to do with the system being broken, any more than libsystemd-login0:i386 did.

The only thing that removing libpam-systemd:i386 from your system does is trigger the code in the prerm:

if [ "$1" = "remove" ] ; then
    pam-auth-update --package --remove systemd
fi

However, this is a *bug* in the libpam-systemd package, because as a multiarch package, it should *not* remove the module from the config until the package is removed for all architectures. (Cf. libpam-cracklib's prerm in trusty.)

So instead of pam being confused by having libpam-systemd:i386 installed, you've broken your pam config by removing libpam-systemd:i386. And in the process, you say that the system started to work.

Without making any further changes to the packages installed, please log out and log back in to confirm that your logind session is still in a working state; and if it is, please attach the /etc/pam.d/common-session from the system.

Then please run 'sudo pam-auth-update --package', log out, log back in again, and tell us whether the suspend/reboot/shutdown options are broken.