#GNOME/#GTK nit:

When I close my Framework laptop on Debian and I have fingerprint support in PAM, it still asks me to use it to do sudo commands and unlock it. Unlocking is fine because it times out but otherwise, I'm kind of annoyed and have to cancel it out.

I guess this is less of a PAM issue and more of a UX issue, to automatically toggle this module when the laptop lid is open or closed.

Makes me think that this could be yet another custom PAM module (if one can just run the toggle dynamically in place of the module) by listening to udev or something
Someone out there who's smarter than me can probably verify this
Oh come on lol this can't be that novel
[PAM] Fail authentication when LID is closed (#403) Β· Issues Β· libfprint / libfprint Β· GitLab

Because how PAM tries modules in order and one by one, if we want fingerprint authentication if will ask for a fingerprint and only when that method fails...

GitLab
@jalcine iirc when I looked into this the β€œsimple” fix was to listen to events and disable/enable the reader device on close/open