Ray Strode 4057a87e05 authPrompt: propagate gdm "reset" signal after user switching ... After a user types in their password at the login screen, one of two things can happen 1) a new session is started 2) an existing session is switched to In the latter case, GDM sends a reset signal to the login screen, so it knows to go back to the user list and wait to be summoned again. Unfortunately, all reset signals are ignored after verification success. The reason is because the reset handler was copied from the unlock dialog as part of a deduplication effort in commit 7e7295f259 and the unlock dialog handler at the time also emitted a "failed" signal on reset (which wouldn't make sense to emit after success). These days "failed" is handled in a different way. This commit changes the code to let reset signals through after successful verification. https://bugzilla.gnome.org/show_bug.cgi?id=710456		2013-11-26 12:48:46 -05:00
..
authPrompt.js	authPrompt: propagate gdm "reset" signal after user switching	2013-11-26 12:48:46 -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: MessageType is now in GdmUtil	2013-10-02 13:58:09 -04:00
oVirt.js	gdm: support pre-authenticated logins from oVirt	2013-10-14 13:54:30 -04:00
realmd.js	gdm: Fix regression where domain login hint not shown	2013-05-03 21:59:57 +02:00
util.js	gdm: support pre-authenticated logins from oVirt	2013-10-14 13:54:30 -04:00