[Touch-packages] [Bug 1291454] Re: spontaneously logged out of lightdm session, authentication failed until logind restarted

2014-10-04 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1291454] Re: spontaneously logged out of lightdm session, authentication failed until logind restarted

2014-08-05 Thread Martin Pitt
I haven't seen this myself, and the lightdm snippet in the description doesn't give a clue what happened. If you have a way to reproduce this, could you please modify /usr/share/dbus-1/system- services/org.freedesktop.systemd1.service like that: Exec=/bin/sh -c 'G_DBUS_DEBUG=all

[Touch-packages] [Bug 1291454] Re: spontaneously logged out of lightdm session, authentication failed until logind restarted

2014-08-05 Thread Steve Langasek
This was probably an upgrade issue at the time. It is certainly not reproducible now. Was logind being correctly restarted on package upgrade? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1291454] Re: spontaneously logged out of lightdm session, authentication failed until logind restarted

2014-08-05 Thread Martin Pitt
Ah, you said out of nowhere and suddenly, so this didn't sound related to doing an upgrade. This would be plausible, of course. In trusty, logind does get restarted during upgrades, but that shouldn't matter unless something like lightdm is specifically listening to logind getting off and back on

[Touch-packages] [Bug 1291454] Re: spontaneously logged out of lightdm session, authentication failed until logind restarted

2014-08-05 Thread Martin Pitt
Thus with the d-bus activation the authentication failed until logind restarted part is fixed in utopic. In trusty, it would have been that way between libpam-systemd being upgraded and not configured yet (as logind wouldn't get auto-started). But that still shouldn't log out existing sessions.