[gnome-shell/gnome-3-28] gdm, util: Always allow to retry login in unlock mode
- From: Marco Trevisan <marcotrevi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-shell/gnome-3-28] gdm, util: Always allow to retry login in unlock mode
- Date: Wed, 25 Jul 2018 20:39:40 +0000 (UTC)
commit fddd122956d01e7672e7a6e3a4ffc9b696d34916
Author: Marco Trevisan (TreviƱo) <mail 3v1n0 net>
Date: Tue May 29 00:10:09 2018 +0000
gdm, util: Always allow to retry login in unlock mode
When in lockscreen mode there's no point of resetting the auth login as there's
no welcome screen, and that would just cause the UI to freeze, with no reason.
This could have been useful if we were stopping the user to login for a given
time after ALLOWED_FAILURES attempts, but this is not the case yet.
(cherry picked from commit cf69fe4b18e9ecf5d33de42c636a42950a1c7cd8)
js/gdm/util.js | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
---
diff --git a/js/gdm/util.js b/js/gdm/util.js
index 0532ca848..105a3207b 100644
--- a/js/gdm/util.js
+++ b/js/gdm/util.js
@@ -534,12 +534,13 @@ var ShellUserVerifier = new Lang.Class({
_verificationFailed(retry) {
// For Not Listed / enterprise logins, immediately reset
// the dialog
- // Otherwise, we allow ALLOWED_FAILURES attempts. After that, we
- // go back to the welcome screen.
+ // Otherwise, when in login mode we allow ALLOWED_FAILURES attempts.
+ // After that, we go back to the welcome screen.
this._failCounter++;
let canRetry = retry && this._userName &&
- this._failCounter < this._settings.get_int(ALLOWED_FAILURES_KEY);
+ (this._reauthOnly ||
+ this._failCounter < this._settings.get_int(ALLOWED_FAILURES_KEY));
if (canRetry) {
if (!this.hasPendingMessages) {
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]