gnome-shell/js/gdm
Michael Catanzaro 15e727e174 loginDialog: fix cancel button in ask for username mode
If the user clicks Not Listed? to enter ask for username mode, clicks
cancel, and then attempts to log in via the user list, the user will see
"Authentication failed" after correctly typing the password, and then
will become stuck in an empty screen with just the gray noise background.

The problem is, we forgot to disconnect from the signal that's waiting
for the next button to be pressed on the username entry screen. Since
the signal handler that executes here is expecting the username to be
input, and isn't prepared for us to have switched back to user list,
various bad things happen. We try to start two gdm-password
conversations at once, for instance, one using the user's password as
the username. I stopped investigating here, because it's easy to fix by
disconnecting from the signal at the right time.

https://bugzilla.gnome.org/show_bug.cgi?id=770328
2016-09-10 16:51:19 -05:00
..
authPrompt.js authPrompt: Do not allow bypassing disabled Sign In button 2016-01-07 17:19:04 -06:00
batch.js batch: Add old commit message as comment at top of file 2015-10-13 14:43:39 -05:00
fingerprint.js Stringify the xml definitions for E4X removal 2013-10-25 08:57:27 +11:00
loginDialog.js loginDialog: fix cancel button in ask for username mode 2016-09-10 16:51:19 -05:00
oVirt.js Stringify the xml definitions for E4X removal 2013-10-25 08:57:27 +11:00
realmd.js Stringify the xml definitions for E4X removal 2013-10-25 08:57:27 +11:00
util.js Revert "Revert "Give user 48ms to read each character of a PAM message, earlier it was 16ms"" 2015-03-27 14:36:05 +01:00