[systemd-devel] Regression: systemd-logind failure after migration to internal dbus impl

Kay Sievers kay at vrfy.org
Thu Nov 7 04:19:54 PST 2013


On Thu, Nov 7, 2013 at 9:34 AM, Oleksii Shevchuk <alxchk at gmail.com> wrote:
> FYI, systemd-logind is still broken as for
> 86198b2788e56fd05959c2dce670d1646bf99bcd.
> Current symptoms: After leaving S3 logind doesn't sent notifications
> about leaving sleep mode. Instead, it goes to failure state:
>
> systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
> systemd[1]: Unit systemd-logind.service entered failed state.
> systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
> systemd[1]: Stopping Login Service...
> systemd[1]: Starting Login Service...

As talked about on IRC, I tried over night, works all fine here.

Are you running i686, and not x86_64?

Kay


More information about the systemd-devel mailing list