0ccb8e27d4
When a verification session has failed we may want to wait for the user to have completed all the waiting queries and to have read all the incoming messages, however during such time an user verifier should not be allowed to queue further messages to the UI, as we're about to completely stop the identification or start a new one. Unfortunately this is not true because we're still connected to the identifier signals, and so we may still show messages. This is particularly true when using the fingerprint PAM module as it may restart the authentication while we're in the process of stopping it. So, keep track of all the signals we've connected to, and disconnect on verification failed and during cancel/clear operations. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1622> |
||
|---|---|---|
| .. | ||
| authPrompt.js | ||
| batch.js | ||
| credentialManager.js | ||
| loginDialog.js | ||
| oVirt.js | ||
| realmd.js | ||
| util.js | ||
| vmware.js | ||