[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.
https://bu
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.
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
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.
https://bugs.l
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 /usr/lib/x86_64-
5 matches
Mail list logo