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>
GNOME Shell
GNOME Shell provides core user interface functions for the GNOME 3 desktop, like switching to windows and launching applications. GNOME Shell takes advantage of the capabilities of modern graphics hardware and introduces innovative user interface concepts to provide a visually attractive and easy to use experience.
For more information about GNOME Shell, including instructions on how to build GNOME Shell from source and how to get involved with the project, see the project wiki.
Bugs should be reported to the GNOME bug tracking system.
Contributing
To contribute, open merge requests at https://gitlab.gnome.org/GNOME/gnome-shell.
Commit messages should follow the GNOME commit message guidelines. We require an URL to either an issue or a merge request in each commit.
License
GNOME Shell is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for details.