After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685143 - Login as "Not listed" -- session chosen at "User" entry ignored
Login as "Not listed" -- session chosen at "User" entry ignored
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: login-screen
3.6.x
Other Linux
: Normal minor
: ---
Assigned To: Ray Strode [halfline]
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-09-30 12:46 UTC by Mantas Mikulėnas (grawity)
Modified: 2013-09-07 02:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mantas Mikulėnas (grawity) 2012-09-30 12:46:20 UTC
In gnome-shell 3.4, 3.5, 3.6.0:

When I use the "Not listed" item at the user chooser, then select a different session before entering the username, the selection is reverted as soon as I hit Enter and the password prompt is displayed and I have to re-do my selection again.
Comment 1 Matthias Clasen 2012-10-01 10:53:04 UTC
The underlying issue is that we should not even ask for the session before we know the user name. Because we only then know if there is an existing session that we must switch to, in which case asking for the session is not useful.
Comment 2 Milan Bouchet-Valat 2012-10-02 08:41:07 UTC
One case where it is necessary to allow choosing a session before we know the user name is if we want to allow password-less login. In that case, once the user name is known, it's too late to select a session, since we're already logging in...
Comment 3 Mantas Mikulėnas (grawity) 2012-10-02 20:09:22 UTC
(In reply to comment #2)
> One case where it is necessary to allow choosing a session before we know the
> user name is if we want to allow password-less login. In that case, once the
> user name is known, it's too late to select a session, since we're already
> logging in...

Isn't it the same problem as with password-less users *in* the list?
Comment 4 Florian Müllner 2013-09-07 02:11:38 UTC
I think this was fixed in bugs 683437 and 706607. Please reopen if you can reproduce the problem with the upcoming 3.10 ...