Fix for "Fingerprint not working after waking up from suspend" doesn't work on Fedora 36
See original GitHub issueFix for “Fingerprint not working after waking up from suspend”
sudo systemctl enable open-fprintd-resume open-fprintd-suspend
doesn’t work on Fedora 36 on Thinkpad T480. Used to be fine before the upgrade to this version system.
Also after waking up from suspend now any command that requires ‘sudo’ in terminal makes the terminal wait around 20 seconds until there is a prompt to type password.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (2 by maintainers)
Top Results From Across the Web
FIngerprint not working after returning from sleep
Re: FIngerprint not working after returning from sleep. Kill the process and restart it ... stop going to sleep ... or stop using...
Read more >Fedora 36 won't wake from sleep since updating to kernel 5.19
I'm am hence avoiding 5.19 kernel but apparently it fixes security stuff so I would like to update. Anyone know a fix for...
Read more >Fingerprint reader stops working after suspend/resume
So it says "swipe your finger, etc." but it doesn't do anything? In this case it's probably the device not being reset properly....
Read more >Fingerprint Reader is disabled when notebook resumes from ...
This is my first 'proper' notebook running Fedora (traditionally use desktop ... Fingerprint sensor doesn't work after waking up from sleep.
Read more >Waking up from suspend #39 - uunicorn/python-validity - GitHub
I don't know if same issue, but after suspend/resume fingerprint is not working directly. I've to wait few seconds (~30 sec). Yes, it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can we please reopen this issue as this is a workaround as mentioned by @gnoamchomsky This is not how things are supposed to work
In regards to comments in #128 here is the output:
Seems to be related to uunicorn/open-fprintd#12