You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(systemd): add robust resume service for sensor re-initialization
Problem
Fingerprint sensor fails to re-initialize correctly after system suspend/hibernate on modern kernels. The python3-validity service loses its connection to the hardware or enters an inconsistent state, preventing fingerprint authentication upon resume.
Solution
Add a dedicated systemd resume service python3-validity-resume.service that explicitly restarts python3-validity.service and open-fprintd.service when the system wakes up. This ensures a clean state for the driver and the fprintd bridge.
Environment Information
Hardware
Device: Synaptics, Inc. Metallica MIS Touch Fingerprint Reader
I have confirmed a reliable, non-invasive fix by creating a dedicated resume service unit. This approach avoids arbitrary delays and modifications to PAM configuration.
Solution Details
Install the following unit file as /etc/systemd/system/python-validity-resume.service:
ExecStartPost: Acts as a D-Bus "readiness gate," ensuring systemd does not report the unit as "finished" until the driver is responsive on the bus. This solves the race condition with login greeters (GDM/SDDM).
No PAM/Sleep: Completely avoids brittle timing hacks or system-wide auth modifications.
changed the title [-]Fingerprint reader fails on resume; insufficient resume strategy[/-][+]Fingerprint reader fails on resume; insufficient resume strategy: proposal fix[/+]on May 17, 2026
P.S.: Great software, btw! Me and my t480 followed for years - and now using for years - the progress to the day its fingerprint sensor would work in linux.
I can confirm this is a real issue on the 138a:0092 sensor (HP EliteBook x360 1030 G2, Fedora 44) as well. After suspend, the USB connection goes stale and the sensor requires a full re-initialization.
The approach in PR #255 (dedicated resume service that restarts both python3-validity and open-fprintd) works well. I'm using the same pattern:
Activity
sidneijp commentedon May 17, 2026
Also tracking relevant discussions in issue #106.
sidneijp commentedon May 17, 2026
I have confirmed a reliable, non-invasive fix by creating a dedicated resume service unit. This approach avoids arbitrary delays and modifications to PAM configuration.
Solution Details
Install the following unit file as /etc/systemd/system/python-validity-resume.service:
Why this works:
[-]Fingerprint reader fails on resume; insufficient resume strategy[/-][+]Fingerprint reader fails on resume; insufficient resume strategy: proposal fix[/+]sidneijp commentedon May 17, 2026
P.S.: Great software, btw! Me and my t480 followed for years - and now using for years - the progress to the day its fingerprint sensor would work in linux.
I'm very thankfull for this project! 🥳
milad-o commentedon May 27, 2026
I can confirm this is a real issue on the
138a:0092sensor (HP EliteBook x360 1030 G2, Fedora 44) as well. After suspend, the USB connection goes stale and the sensor requires a full re-initialization.The approach in PR #255 (dedicated resume service that restarts both
python3-validityandopen-fprintd) works well. I'm using the same pattern:The D-Bus readiness gate in
ExecStartPostis key — without it, SDDM/KDE's lock screen may try to authenticate before the driver is back online.+1 to merging #255 or a variant of it into the main project.