Bug 1005233 - lightdm doesn't check state of existing user sessions
Summary: lightdm doesn't check state of existing user sessions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lightdm-gtk
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-06 13:32 UTC by Dan Mashal
Modified: 2013-09-23 00:38 UTC (History)
12 users (show)

Fixed In Version: systemd-207-3.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 14:44:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dan Mashal 2013-09-06 13:32:48 UTC
1) Install MATE + Cinnamon

2) Login to MATE

3) Logout or switch users

4) Try to login to Cinnamon

5) ???

6) Profit!!

Comment 1 Rex Dieter 2013-09-17 12:10:29 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.

Comment 2 Rex Dieter 2013-09-17 16:45:09 UTC
Retested with systemd-207-3.fc20 still reproducible.

Reassigning to systemd, adjusting summary accordingly.

Comment 3 Fedora Update System 2013-09-17 16:45:48 UTC
systemd-207-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/systemd-207-3.fc20

Comment 4 Harald Hoyer 2013-09-17 16:58:16 UTC
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.

Comment 5 Rex Dieter 2013-09-17 17:03:59 UTC
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.

Comment 6 Harald Hoyer 2013-09-17 17:27:28 UTC
(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?

Comment 7 Fedora Update System 2013-09-17 18:16:10 UTC
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).

Comment 8 Rex Dieter 2013-09-17 18:43:22 UTC
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.

Comment 9 Rex Dieter 2013-09-19 14:44:56 UTC

*** This bug has been marked as a duplicate of bug 998490 ***

Comment 10 Fedora Update System 2013-09-23 00:38:45 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.