logind flags wrong session as active
Bug #1415104 reported by
Sebastien Bacher
This bug affects 16 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
In vivid I'm regularly running in an issue where, after an upgrade, logind considers my current session as not-active (resulting in unwanted polkit prompt for common actions in the session)
I've updated my system using update-manager and restarted my session (logout to unity-greeter and back in)
loginctl list-sessions lists 2 sessions for my user, an old one with hanging chromium processes, which is flagged as active, and my current one marked as active = no
Changed in systemd (Ubuntu): | |
status: | Triaged → In Progress |
To post a comment you must log in.
This is quite easy to reproduce indeed:
* Start computer/VM, log in; session c1 (with autologin) or c2 (with manual login) should be the active one.
* Log out and back in; now c1 should be in state "closing", assuming that there is still some leftover process in it. In my case that's "pulseaudio" (in Seb's case there was some more cruft). The status is still right, c1 is closing, c3 is active.
* sudo systemctl restart systemd-logind; now c1 becomes "active yes/opening", and c3 is "active no/online".
I guess logind sets the status of all existing sessions at startup (which makes sense), and since both sessions have the same VT/Display it probably just considers the first matching one as active.