summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBenjamin Berg <bberg@redhat.com>2021-04-28 18:32:22 +0200
committerRay Strode <rstrode@redhat.com>2021-04-28 13:19:28 -0400
commite765e58e54f1200229190246b2c57c716f126cb2 (patch)
treef7ff94eeacbe18dd796a16a0c5f1015e899f5fd5
parent9157969ab83526a8a40e624d044d857459793768 (diff)
downloadgnome-shell-benzea/fix-password-login-after-bg-failure.tar.gz
gdm: Remove pending fingerprint verification failurebenzea/fix-password-login-after-bg-failure
It can happen that we get a problem report and a verification failure at the same time. For fingerprint, a problem report can result in an internal verification failure to be queued. Remove this queued failure again if we got a failure already from GDM directly.
-rw-r--r--js/gdm/util.js5
1 files changed, 5 insertions, 0 deletions
diff --git a/js/gdm/util.js b/js/gdm/util.js
index ecaf09b6a..72561daab 100644
--- a/js/gdm/util.js
+++ b/js/gdm/util.js
@@ -686,6 +686,11 @@ var ShellUserVerifier = class {
}
_verificationFailed(serviceName, shouldRetry) {
+ if (serviceName === FINGERPRINT_SERVICE_NAME) {
+ if (this._fingerprintFailedId)
+ GLib.source_remove(this._fingerprintFailedId);
+ }
+
// For Not Listed / enterprise logins, immediately reset
// the dialog
// Otherwise, when in login mode we allow ALLOWED_FAILURES attempts.