b916df1110
When we cancel an user authentication via Escape key or cancel button on AuthPrompt we reset the view and we emit a 'cancelled' signal that leads to destroying the auth prompt and the user verifier. However, the verifier may still have an operation in progress and its completion may take some time (as in the case of gdm-fingerprint), but we just leave the gdm worker running until its pam module completes (potentially never) clearing and disposing its handle. So, instead of just clearing the verify, actually cancel and clear it. In case the user verifier is set, clearing the relevant data will happen anyway as part of the cancel() call. Ideally this would have been handled by gdm itself, but unfortunately we can't fix it there because the verifier itself is a class generated by gdbus-codegen, so we can't handle this automatically on disposal nor we can automatically monitor when the caller proxy is stopped on our side. Fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 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 | ||