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

2013-11-10 Thread Lennart Poettering
On Sat, 09.11.13 16:17, Oleksii Shevchuk (alx...@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:

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

2013-11-09 Thread Oleksii Shevchuk
> 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: So, the problem is: sd_event_run(m->event, us) at manager_run@login.c retur

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

2013-11-07 Thread Kay Sievers
On Thu, Nov 7, 2013 at 9:34 AM, Oleksii Shevchuk 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]: sys

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

2013-11-07 Thread Oleksii Shevchuk
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/FAI