I just noticed that I have the same exact issue. I am running Ubuntu 16.04 Desktop, I enabled multiarch support and I am running 32 bit installation with 64 bit kernel.
May 24 12:59:13 kenn systemd-logind[1680]: Failed to send delayed message: Unit suspend-to-hibernate.service not found.
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Unit entered failed state.
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
May 24 12:59:13 kenn systemd[1]: Stopped Login Service.
May 24 12:59:13 kenn systemd[1]: Starting Login Service...
I just noticed that I have the same exact issue. I am running Ubuntu 16.04 Desktop, I enabled multiarch support and I am running 32 bit installation with 64 bit kernel.
May 24 12:59:13 kenn systemd- logind[ 1680]: Failed to send delayed message: Unit suspend- to-hibernate. service not found. logind. service: Main process exited, code=exited, status=1/FAILURE logind. service: Unit entered failed state. logind. service: Failed with result 'exit-code'. logind. service: Service has no hold-off time, scheduling restart.
May 24 12:59:13 kenn systemd[1]: systemd-
May 24 12:59:13 kenn systemd[1]: systemd-
May 24 12:59:13 kenn systemd[1]: systemd-
May 24 12:59:13 kenn systemd[1]: systemd-
May 24 12:59:13 kenn systemd[1]: Stopped Login Service.
May 24 12:59:13 kenn systemd[1]: Starting Login Service...