1) Install MATE + Cinnamon 2) Login to MATE 3) Logout or switch users 4) Try to login to Cinnamon 5) ??? 6) Profit!!
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.