Recompile fprintd to decrease timeout
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
This commit is contained in:
parent
42992f35e3
commit
358732f4bd
|
@ -52,6 +52,8 @@ So, to recap, the bug actually has isn't KDE Plasma's fault. I guess it's an `fp
|
|||
|
||||
Another potential problem is that `fprintd` waits around 30 seconds after a successful login before quitting, so sleeping and waking up and sleeping and waking up can cause the bug to reappear during the second wake-up, but I don't think I'd ever run into this corner case except while debugging this bug. When debugging, I had to manually run `sudo killall fprintd` between sleep-wake up tests.
|
||||
|
||||
Maybe there's a better way to solve this. If you know of a better solution, please let me know!
|
||||
It turns out the 30 second timeout is [hardcoded in the source code](https://gitlab.freedesktop.org/libfprint/fprintd/-/blob/master/src/fprintd.h?ref_type=heads#L29), so I changed it to 1 and recompiled, which fixed this problem. I might try contributing this fix to fprintd, but maybe they have a reason for 30 as the default. Also, fprintd doesn't seem actively maintained anymore.
|
||||
|
||||
Maybe there's a better way to solve this. If you know of a better solution, please let me know! It's definitely a bit upsetting that I need to mess with PAM config files, udev rules, systemd override files, and recompile fprintd to get my fingerprint reader to work properly, but I guess that's the struggle of Linux sometimes. I wish Lenovo could provide better support for Linux on my laptop model, since they do sell a preinstalled Ubuntu version of that model.
|
||||
|
||||
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)!
|
||||
|
|
Loading…
Reference in a new issue