I can reproduce a very similar issue on a completely different system: - **Hardware:** Lenovo ThinkPad X380 Yoga - **OS:** Arch Linux - **Desktop:** GNOME 51.1 - **Fingerprint sensor:** Validity 138a:009d, using python-validity and open-fprintd
The important difference is that **suspend/resume is not required to trigger the problem**. On my system, the issue occurs consistently, even when simply locking the screen with **Super+L**, without any prior suspend. The lock screen becomes unusable and normal authentication is no longer possible. Fingerprint authentication itself works correctly elsewhere, including with sudo. This suggests that the underlying problem might not be related to suspend/resume or a particular fingerprint sensor, but rather to GNOME's lock screen authentication handling. It might therefore be useful to investigate whether the issue can also be reproduced by locking the screen directly, without suspending the system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172157 Title: Lock screen gets stuck after resume with fingerprint enabled: no password entry, fingerprint not accepted, no feedback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2172157/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
