touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

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.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu)
       Status: New => Triaged

** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1415104

Title:
  logind flags wrong session as active

Status in systemd package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1415104/+subscriptions