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 746180 - Weird behavior when using "Not Listed?" and not entering any username
Weird behavior when using "Not Listed?" and not entering any username
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: login-screen
3.15.x
Other Linux
: Normal minor
: ---
Assigned To: Michael Catanzaro
gnome-shell-maint
: 760185 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-03-13 19:53 UTC by Michael Catanzaro
Modified: 2016-01-08 00:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (1.19 KB, patch)
2016-01-07 22:14 UTC, Michael Catanzaro
none Details | Review
patch (1.24 KB, patch)
2016-01-07 22:15 UTC, Michael Catanzaro
committed Details | Review

Description Michael Catanzaro 2015-03-13 19:53:27 UTC
Testing F22 Workstation Alpha. On the login screen, I click "Not Listed?" and then click Sign In without entering any username. The Sign In button changes to read Next, and the session selection gear menu appears next to it. Then I click Next, and it changes to read Sign In again. Then I click Sign In, and it takes me back to the login screen.

I was going to say the expected behavior would be to prohibit pressing the button if no characters have been entered in the username entry, but:

halfline:  well blank username technically is "legal"
halfline:  but maybe we should forbid it anyway
halfline:  and clearly the state machine is getting kind of hosed up from your description
halfline:  but yea, one thing about pam is the input username doesn't have to equal the output username, and some pam modules treat blank username special (though none of the ones we care about for the log in as another user feature)
Comment 1 Michael Catanzaro 2016-01-05 21:11:51 UTC
If you just click cancel, half the time it seems to work properly, but half the time you get the username prompt over top of the user list.
Comment 2 Michael Catanzaro 2016-01-07 21:41:23 UTC
Just for the record, this is also causing:

AccountsService-CRITICAL **: act_user_manager_get_user: assertion 'username != NULL && username[0] != '\0'' failed
Comment 3 Michael Catanzaro 2016-01-07 22:14:30 UTC
Created attachment 318444 [details] [review]
patch
Comment 4 Michael Catanzaro 2016-01-07 22:15:22 UTC
Created attachment 318445 [details] [review]
patch
Comment 5 Florian Müllner 2016-01-07 22:16:09 UTC
*** Bug 760185 has been marked as a duplicate of this bug. ***
Comment 6 Florian Müllner 2016-01-07 22:17:47 UTC
Review of attachment 318445 [details] [review]:

OK