** Description changed: + [ Test case ] + In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat - You'll see by checking watch -n1 "ps aux |grep gdm-session-worker" (or - just ps'ing after unlocked) that many gdm workers are left around and - never terminated. + Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing + after unlocked) gdm workers should not be running (a part the one used + for logging in). Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 + + [ Regression potential ] + + Authenticating at login screen or at unlock screen stops working after + wrong credentials have been used once or the request has been cancelled + via escape key.
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915066 Title: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915066/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
