OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
audio-input medium occasional DISPUTE

Fix a fingerprint reader that stops working after the first suspend

omarchyarchendeavouroscachyosmanjarohyprlandwaylandlaptop
AUDITED Audited against its sources and confirmed accurate.

Symptom

The fingerprint reader works after boot but stops after the first suspend/resume: fprintd-verify hangs or errors, and login prompts hang for ~10 seconds before falling back to a password. Sometimes reported as the login screen freezing when revealing the password prompt after resume.

Cause

fprintd keeps running for ~30 seconds after a successful auth. Suspending in that window wedges it. Separately, some USB readers are re-enumerated on resume and fprintd holds a stale handle because USB persistence is off for that device.

Fix

Kill fprintd before every sleep:


# /etc/systemd/system/kill-fprintd.service
[Unit]
Description=Kill fprintd before sleep
Before=sleep.target

[Service]
ExecStart=killall fprintd

[Install]
WantedBy=sleep.target

sudo systemctl daemon-reload
sudo systemctl enable kill-fprintd.service

If the reader is re-enumerated on resume, enable USB persistence for it. Get the vendor/product IDs from lsusb and substitute them:


lsusb | grep -i -E 'fingerprint|synaptics|goodix|elan|validity'

# /etc/udev/rules.d/01-fingerprint.rules
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="06cb", ATTRS{idProduct}=="00fc", ATTR{power/persist}="1", RUN="/usr/bin/chmod 444 %S%p/../power/persist"

sudo udevadm control --reload-rules
sudo udevadm trigger

Upstream also recommends s2idle rather than S3 for these readers. Check what your machine uses:


cat /sys/power/mem_sleep

Verify

systemctl suspend, resume, then fprintd-verify succeeds immediately without a hang.

Sources

fprintd-broken-after-suspend