Comment 92 for bug 1766137

Revision history for this message
Marco Trevisan (TreviƱo) (3v1n0) wrote :

I think the issue is getting is there but maybe different from the one originating this bug, so maybe to be handled in a different one...

So please, test this:

 1. Create another user
 2. Login with your user (or the other, as you wish)
 3. Lock the session -> Switch to other user from lockscreen
 4. Once back on GDM, select another user... Then you can login and redo what
    said in 3. or just go back.
 5. From GDM, again try to unlock the 1st user, it fails.

Also `ps aux | grep <the-user-logged-in>` shows running processes for that session, while gdm seems to try to initialize a new one.

Anyway, while it's true this could be a regression of this change, I think it might be still better to release the version we have in proposed as this kind of issue can be handled in a different bug.
In any case I'm looking at it right now.