Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Fingerprint reader fails after suspend: fprintd reports "Cannot run while suspended"
Reported by hojner · filed Aug 17, 2026Closed upstream on 2026-10-04 by the merge of PR #7158 (closed by dhh). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Description
After the system suspends and resumes, the fingerprint reader stops working on the lock screen. The lock screen's fingerprint prompt either hangs or immediately fails, forcing password fallback.
Steps to Reproduce
- Unlock the lock screen using fingerprint — works fine
- Let the system suspend (via idle, lid close, or
Super+Ctrl+Lthen suspend) - Resume the system
- Lock screen appears — attempt to use fingerprint to unlock
- Fingerprint authentication fails / is unresponsive
Expected Behavior
Fingerprint authentication works on the lock screen after resume from suspend.
Actual Behavior
fprintd reports the device error and authentication fails silently:
fprintd[PID]: Device reported an error during verify: Cannot run while suspended.This appears in journalctl -u fprintd consistently after every suspend/resume cycle. The error persists until fprintd is manually restarted (systemctl restart fprintd), after which fingerprint works again.
Root Cause
fprintd holds a stale/broken device handle after the fingerprint reader is suspended by the kernel. On resume, fprintd doesn't re-probe the device — it just fails all verify calls until restarted.
Suggested Fix
Add a /lib/systemd/system-sleep/restart-fprintd hook (following the same pattern as the existing unmount-fuse hook in that directory) to restart fprintd a few seconds after resume:
#!/bin/bash
# Restart fprintd after resume so the fingerprint reader recovers from suspend.
if [[ $1 == "post" ]]; then
(sleep 3; systemctl restart fprintd.service) &
fiThe 3-second delay gives the device time to re-enumerate before fprintd tries to claim it. Manually running systemctl restart fprintd after each resume confirms this fix works.
System Details
| Field | Value |
|---|---|
| Omarchy version | 4.0.0-1 |
| Kernel | 7.1.8-arch1-3 |
| CPU | Intel Core Ultra 7 155U (Meteor Lake) |
| GPU | Intel Meteor Lake-P (integrated) |
| Fingerprint sensor | Goodix MOC Fingerprint Sensor (integrated) |
| fprintd | 1.94.5-2 |
| libfprint | 1.94.100-1 |
Relevant Logs
Aug 16 00:17:15 fprintd[24755]: Device reported an error during verify: Cannot run while suspended.
Aug 16 11:28:54 fprintd[69990]: Device reported an error during verify: Cannot run while suspended.
Aug 17 (multiple occurrences after each suspend/resume cycle)View raw text
## Description After the system suspends and resumes, the fingerprint reader stops working on the lock screen. The lock screen's fingerprint prompt either hangs or immediately fails, forcing password fallback. ## Steps to Reproduce 1. Unlock the lock screen using fingerprint — works fine 2. Let the system suspend (via idle, lid close, or `Super+Ctrl+L` then suspend) 3. Resume the system 4. Lock screen appears — attempt to use fingerprint to unlock 5. Fingerprint authentication fails / is unresponsive ## Expected Behavior Fingerprint authentication works on the lock screen after resume from suspend. ## Actual Behavior `fprintd` reports the device error and authentication fails silently: ``` fprintd[PID]: Device reported an error during verify: Cannot run while suspended. ``` This appears in `journalctl -u fprintd` consistently after every suspend/resume cycle. The error persists until `fprintd` is manually restarted (`systemctl restart fprintd`), after which fingerprint works again. ## Root Cause `fprintd` holds a stale/broken device handle after the fingerprint reader is suspended by the kernel. On resume, `fprintd` doesn't re-probe the device — it just fails all verify calls until restarted. ## Suggested Fix Add a `/lib/systemd/system-sleep/restart-fprintd` hook (following the same pattern as the existing `unmount-fuse` hook in that directory) to restart `fprintd` a few seconds after resume: ```bash #!/bin/bash # Restart fprintd after resume so the fingerprint reader recovers from suspend. if [[ $1 == "post" ]]; then (sleep 3; systemctl restart fprintd.service) & fi ``` The 3-second delay gives the device time to re-enumerate before `fprintd` tries to claim it. Manually running `systemctl restart fprintd` after each resume confirms this fix works. ## System Details | Field | Value | |-------|-------| | Omarchy version | 4.0.0-1 | | Kernel | 7.1.8-arch1-3 | | CPU | Intel Core Ultra 7 155U (Meteor Lake) | | GPU | Intel Meteor Lake-P (integrated) | | Fingerprint sensor | Goodix MOC Fingerprint Sensor (integrated) | | fprintd | 1.94.5-2 | | libfprint | 1.94.100-1 | ## Relevant Logs ``` Aug 16 00:17:15 fprintd[24755]: Device reported an error during verify: Cannot run while suspended. Aug 16 11:28:54 fprintd[69990]: Device reported an error during verify: Cannot run while suspended. Aug 17 (multiple occurrences after each suspend/resume cycle) ```
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.