[gnome-shell/gnome-3-10] authPrompt: propagate gdm "reset" signal after user switching
- From: Ray Strode <halfline src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-shell/gnome-3-10] authPrompt: propagate gdm "reset" signal after user switching
- Date: Tue, 26 Nov 2013 17:48:57 +0000 (UTC)
commit 4057a87e058bceafbb0a691b04af3c44ea50cb6d
Author: Ray Strode <rstrode redhat com>
Date: Mon Nov 25 22:30:53 2013 -0500
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
7e7295f259febf34c89659a9bcb05f9924fa1976 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
js/gdm/authPrompt.js | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
---
diff --git a/js/gdm/authPrompt.js b/js/gdm/authPrompt.js
index 1880e36..996b363 100644
--- a/js/gdm/authPrompt.js
+++ b/js/gdm/authPrompt.js
@@ -263,10 +263,8 @@ const AuthPrompt = new Lang.Class({
},
_onReset: function() {
- if (this.verificationStatus != AuthPromptStatus.VERIFICATION_SUCCEEDED) {
- this.verificationStatus = AuthPromptStatus.NOT_VERIFYING;
- this.reset();
- }
+ this.verificationStatus = AuthPromptStatus.NOT_VERIFYING;
+ this.reset();
},
addActorToDefaultButtonWell: function(actor) {
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]