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 the bus. In general you can kill logind just fine without any ill effects. The exception might be if you dist- upgraded from a very old version that had a different format in /run/systemd/ but that sounds implausible with an intra-trusty upgrade to 204-5ubuntu13 (there were lots of 204 versions before).
In utopic there is no init script/job for logind at all any more, it's all D-BUS activated. But independently of the mechanics, killing logind shouldn't interfere with the system at all. Does it for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291454 Title: spontaneously logged out of lightdm session, authentication failed until logind restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1291454/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
