This bug was fixed in the package systemd - 218-7ubuntu1
---
systemd (218-7ubuntu1) vivid; urgency=medium
* Merge with Debian unstable. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
- Keep our much
http://cgit.freedesktop.org/systemd/systemd/commit/?id=be94d9549
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415104
Titl
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415104
Title:
logind flags wrong session as active
To manage notifications about
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 "pulseaud
** Attachment added: "details of the hanging session"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1415104/+attachment/4306603/+files/oldsession
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Attachment added: "the current session"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1415104/+attachment/4306611/+files/nsession
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415104
** Attachment added: "the active session"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1415104/+attachment/4306604/+files/osession
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415104
T
