Bug 1005233
| Summary: | lightdm doesn't check state of existing user sessions | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Mashal <dan.mashal> |
| Component: | lightdm-gtk | Assignee: | Rex Dieter <rdieter> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | christoph.wickert, dan.mashal, gregor, harald, johannbg, lnykryn, msekleta, plautrba, rdieter, systemd-maint, vpavlin, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-207-3.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-19 14:44:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dan Mashal
2013-09-06 13:32:48 UTC
systemd loginctl bug as far as I can tell. When you log out (tested using all available DM's including gdm, kdm, lightdm, sddm), according to loginctl your session is still active. So, when you logout, lightdm-gtk thinks you have a current session, and gives the option to "Unlock" that last logged-out user. Workaround for now, in userlist dropdown, choose "Other", and specify your username/password to relogin, using the DE of your choice. Retested with systemd-207-3.fc20 still reproducible. Reassigning to systemd, adjusting summary accordingly. systemd-207-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-207-3.fc20 you should check with: # loginctl show-session <session-id> … Active=no State=closing … According to Lennart, the session is in State=closing for some time, until pulseaudio exits. Ah! show-session does indeed list as State=closing processes still running as me include: systemd --user (sd-pam) gnome-keyring-daemon --daemonize --login If I wait a bit... gnome-kerying-daemon goes away, and so does the session. Hrm... this is a problem for lightdm-gtk, the login screen seems to assume a locked session in this case. This may be causing wierdness with sddm too. I'll test some more. (In reply to Rex Dieter from comment #5) > Ah! > > show-session does indeed list as > State=closing > > processes still running as me include: > > systemd --user > (sd-pam) > gnome-keyring-daemon --daemonize --login > > If I wait a bit... gnome-kerying-daemon goes away, and so does the session. > > > Hrm... this is a problem for lightdm-gtk, the login screen seems to assume a > locked session in this case. This may be causing wierdness with sddm too. > I'll test some more. Why doesn't it check the state of Active? Package systemd-207-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-207-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16966/systemd-207-3.fc20 then log in and leave karma (feedback). Looks like lightdm naively assumes if user Session exists, you can switch-to/unlock it. It doesn't check its state. bouncing back to lightdm. *** This bug has been marked as a duplicate of bug 998490 *** systemd-207-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |