a/website
1
2
Fork 1
Code Issues Pull requests Projects Releases Wiki Activity

Weird fprintd errors, fprintd is the one disabling persist
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Details

Browse source
This commit is contained in:
Anthony Wang 2024-03-21 19:45:33 -04:00
parent 187d538193
commit ddf798fdb4
Signed by: a
SSH key fingerprint: SHA256:B5ADfMCqd2M7d/jtXDoihAV/yfXOAbWWri9+GdCN4hQ
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
content/posts/plasma-6-fingerprint-bug.md
View file

@ -64,4 +64,16 @@ ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="06cb", ATTRS{
I noticed that this kept on getting disabled for some reason after each wake-up, so I changed the file to have permissions 444 to stop that. With this solution, I no longer need the systemd override anymore, but still need to recompile fprintd which is annoying.
Edit 2: I was trying to investigate why I still needed to recompile fprintd. The unpatched version gives this error if I sleep then resume while `fprintd` is still running in the background:
```
Mar 21 19:27:44 ThinkPad-X1-Yoga-Gen-6 kscreenlocker_greet[16753]: pam_fprintd(kde-fingerprint:auth): debug on
Mar 21 19:27:44 ThinkPad-X1-Yoga-Gen-6 kscreenlocker_greet[16753]: pam_fprintd(kde-fingerprint:auth): debug on
Mar 21 19:27:44 ThinkPad-X1-Yoga-Gen-6 kscreenlocker_greet[16753]: pam_fprintd(kde-fingerprint:auth): /net/reactivated/Fprint/Device/0 prints registered: 2
Mar 21 19:27:44 ThinkPad-X1-Yoga-Gen-6 kscreenlocker_greet[16753]: pam_fprintd(kde-fingerprint:auth): Using device /net/reactivated/Fprint/Device/0 (out of 1 devices)
Mar 21 19:27:44 ThinkPad-X1-Yoga-Gen-6 kscreenlocker_greet[16753]: pam_fprintd(kde-fingerprint:auth): failed to claim device Open failed with error: The device is still busy with another operation, please try again later.
```
Also, it seems like fprintd is the one trying to [disable USB persist](https://gitlab.freedesktop.org/libfprint/fprintd/-/blob/master/NEWS#L36) for some reason. If anyone has further insights into these problems, I'd love to hear it!
Oh, and if you managed to reach the end of this post and understood everything, congratulations, you deserve a bowl of [Biángbiáng noodles](https://functional.cafe/@loke/112120713973565564)!