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.
Lock screen: endless 250 ms fingerprint retry against a wedged fprintd device, never recovers
Reported by niclogin · filed Sep 12, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #9648 (R-1097). 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
Environment
- omarchy 4.0.1-1 (Arch Linux)
- fprintd 1.94.5-2, libfprint 1.94.100-1
- kernel 7.1.9-arch1-2
- Laptop with a Synaptics Prometheus MIS Touch Fingerprint Reader (USB 06cb:00bd)
Symptom
After the fingerprint sensor drops off the USB bus (sleep/hibernate/autosuspend, or even plain screen-lock timeout cycles), the lock screen can never unlock with a fingerprint again until fprintd.service is manually restarted. Password still works.
Root cause
fprintd ends up holding two device objects for one physical sensor (/net/reactivated/Fprint/Device/0 and /net/reactivated/Fprint/Device/2). The stale object stays permanently claimed. Every pam_fprintd verify then gets Authorization denied ... Claim ... Device was already claimed, so the fingerprint PAM fails instantly. systemctl restart fprintd collapses the objects back to one and the fingerprint immediately works again.
What the shell does (this issue)
While locked, Service.qml (startFingerprint() + fingerprintRetryTimer, 250 ms interval) restarts the fingerprint PAM auth on every failure for as long as the screen is locked. Each retry fires fresh Claim calls — observed ~37 denied claims within 11 s for a single lock session. This
- never gives up and never recovers the daemon,
- spams the fprintd journal with Device was already claimed,
- keeps re-hitting the same wedged device object.
Suggested fix
On persistent fingerprint failure during lock, recover the device state: after N consecutive failures, restart fprintd.service and resume the attempt (the daemon is idle-deactivatable, cheap to restart). At minimum, back off the retry loop so a wedged sensor stops hammering the daemon.
Reproduction
1. Lock the screen (via timeout or keybind).
2. Suspend the laptop (or let the sensor drop off USB).
3. Wake up. Lock screen shows; try fingerprint → rejected; journalctl -u fprintd fills with Device was already claimed.
4. sudo systemctl restart fprintd → fingerprint works immediately, device list collapses from two objects to one.
Note: the underlying stale-object bug in fprintd is being reported separately to libfprint/fprintd upstream.
View raw text
**Environment** - omarchy 4.0.1-1 (Arch Linux) - fprintd 1.94.5-2, libfprint 1.94.100-1 - kernel 7.1.9-arch1-2 - Laptop with a Synaptics Prometheus MIS Touch Fingerprint Reader (USB `06cb:00bd`) **Symptom** After the fingerprint sensor drops off the USB bus (sleep/hibernate/autosuspend, or even plain screen-lock timeout cycles), the lock screen can never unlock with a fingerprint again until `fprintd.service` is manually restarted. Password still works. **Root cause** fprintd ends up holding two device objects for one physical sensor (`/net/reactivated/Fprint/Device/0` and `/net/reactivated/Fprint/Device/2`). The stale object stays permanently claimed. Every `pam_fprintd` verify then gets `Authorization denied ... Claim ... Device was already claimed`, so the fingerprint PAM fails instantly. `systemctl restart fprintd` collapses the objects back to one and the fingerprint immediately works again. **What the shell does (this issue)** While locked, `Service.qml` (`startFingerprint()` + `fingerprintRetryTimer`, 250 ms interval) restarts the fingerprint PAM auth on every failure for as long as the screen is locked. Each retry fires fresh `Claim` calls — observed ~37 denied claims within 11 s for a single lock session. This - never gives up and never recovers the daemon, - spams the fprintd journal with `Device was already claimed`, - keeps re-hitting the same wedged device object. **Suggested fix** On persistent fingerprint failure during lock, recover the device state: after N consecutive failures, restart `fprintd.service` and resume the attempt (the daemon is idle-deactivatable, cheap to restart). At minimum, back off the retry loop so a wedged sensor stops hammering the daemon. **Reproduction** 1. Lock the screen (via timeout or keybind). 2. Suspend the laptop (or let the sensor drop off USB). 3. Wake up. Lock screen shows; try fingerprint → rejected; `journalctl -u fprintd` fills with `Device was already claimed`. 4. `sudo systemctl restart fprintd` → fingerprint works immediately, device list collapses from two objects to one. Note: the underlying stale-object bug in fprintd is being reported separately to libfprint/fprintd upstream.
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
- Related PRpr/10393· confirmed
- Related PRpr/12461· confirmed
- Fixed bypr/11273· confirmed
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.