[systemd-bugs] [Bug 89834] logind: when a user logs out and immediately back in again, user at .service might stay stopped

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=89834

--- Comment #2 from Jesse McClure <jmcclure at cns.umass.edu> ---
This looks like an issue being discussed on the archlinux forms here:
https://bbs.archlinux.org/viewtopic.php?pid=1548346#p1548346

The logs there in a malfunctioning instance *lack* this journalctl entry:
> Jul 27 18:27:40 Think systemd-logind[287]: Removed session c2.

Which subsequently prevents these entries which are in a working case but
absent from the malfunctioning case:
> Jul 27 18:27:45 Think systemd-logind[287]: New session c3 of user username.
> Jul 27 18:27:45 Think systemd[1]: Started Session c3 of user username.
> Jul 27 18:27:45 Think systemd[1]: Starting Session c3 of user username.

In the malfunctioning case I get this instead:
> Jul 27 18:28:41 Think login[517]: pam_systemd(login:session): Cannot create session: Already occupied by a session

This seems to be triggered by any number of backgrounded processes including
gpg-agent, a detachted tmux session, or dbus-launch.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150730/6b06c68e/attachment.html>