On Wed, 2016-05-11 at 12:06 +0200, Michael Biebl wrote: > Hi James > > On Thu, 15 Oct 2015 10:55:05 -0700 James Bottomley > <james.bottom...@hansenpartnership.com> wrote: > > On Thu, 2015-10-15 at 19:45 +0200, Michael Biebl wrote: > > > Btw, in both cases (#770135 and #793814) the users have been > > > restarting > > > the dbus daemon. You mentioned that you did not do that. > > > > > > So I'm not sure if it's actually the same issue after all and > > > your > > > problem should be tracked as a separate issue. > > > > I'm starting to think it's a logind robustness problem. I traced > > back > > through the logs to the first instance after reboot and this is > > what I > > find: > > .. > > Logind is still active and replies later in the trace, so it looks > like > > dbus either dropped a message or did some type of unexpected > > disconnect. > > After this, logind works until it can't abandon the session, then > > it > > never replies on the bus again. So I suspect somewhere in the > > error > > handling inside logind it doesn't cope with unexpected loss of dbus > > messages. > > We recently had this upstream bug report, which looks like it could > be > relevant: > https://github.com/systemd/systemd/issues/1961 > > Do you see session scopes piling up on your system?
bedivere:~# ls -ld /run/systemd/system/session-*|wc -l 141 So apparently, yes.
signature.asc
Description: This is a digitally signed message part
