gnome-shell/js/gdm
Ray Strode 1ae0fadbf4 loginDialog: don't rely on PAM to ask for a username
For the "Not Listed?" case we will need to be able
to identify when the user has entered their username.

Once we have a way of tracking when the username is
entered, we can then defer showing the session list
too early, before the user can reliably pick a
session.

This username tracking will also be important for
implementing a disable-user-list configuration key.
If the config key gets toggled off at runtime, we'll
need to know if we're at a disruptive part of
the authentication process or not, so we know whether
we can can expose the user list right away, or wait
until the authentication conversation finishes.

Right now, we pass null in for an initial username,
and let the PAM machinery ask the user, which means we
have no good way of knowing when the username is entered.

This commit changes the "Not Listed?" code to ask the
user their username up front, before starting the PAM
conversation in much the same way we do if the user
picks a user from the user list.

https://bugzilla.gnome.org/show_bug.cgi?id=660660
2012-11-06 15:02:36 -05:00
..
batch.js Port all classes with inheritance to class framework 2011-11-24 09:50:04 +01:00
fingerprint.js fingerprint: autostart fprintd when necessary 2012-09-14 12:12:46 -04:00
loginDialog.js loginDialog: don't rely on PAM to ask for a username 2012-11-06 15:02:36 -05:00
powerMenu.js powerMenu: Use LoginManager for suspend 2012-10-23 21:14:10 +02:00
realmd.js gdm: Add network login hint 2012-08-21 13:15:29 -04:00
util.js ShellUserVerifier: fix fail counter 2012-10-29 17:54:12 +01:00