<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - logind: when a user logs out and immediately back in again, user@.service might stay stopped" href="https://bugs.freedesktop.org/show_bug.cgi?id=89834#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - logind: when a user logs out and immediately back in again, user@.service might stay stopped" href="https://bugs.freedesktop.org/show_bug.cgi?id=89834">bug 89834</a> from <a class="email" href="mailto:jmcclure@cns.umass.edu" title="Jesse McClure <jmcclure@cns.umass.edu>"> Jesse McClure</a> <pre>This looks like an issue being discussed on the archlinux forms here: <a href="https://bbs.archlinux.org/viewtopic.php?pid=1548346#p1548346">https://bbs.archlinux.org/viewtopic.php?pid=1548346#p1548346</a> 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>