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.
Rapid lock-screen fingerprint retries can leave the reader unusable
Reported by NeroSong · filed Sep 2, 2026Closed upstream on 2026-09-02 by its own reporter NeroSong, as a duplicate of #9657. 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
System details
HONOR MagicBook Pro 14 2026; Omarchy 4.0.2-1; fprintd 1.94.5; libfprint 1.94.100 with an experimental SDCP fingerprint backend.
What's wrong?
What happened
This occurs intermittently, not on every lock.
The trigger I observed was:
1. Lock the session.
2. Let the lock screen automatically turn the display off.
3. Wake the display with the keyboard and try fingerprint unlock.
On affected attempts, fingerprint authentication quickly fails with a device-integrity error. The lock screen keeps starting new fingerprint PAM sessions, and the kernel repeatedly resets the USB reader. Password unlock remains available.
Why this looks like a lock-screen issue
When the reader returns a fast transient failure, retrying fingerprint PAM every 250 ms appears to keep the device in an unusable state: each new attempt can trigger another USB reset before the reader has recovered. Stopping the rapid retries allows it to recover in most cases.
Local mitigation
I added a small backoff for fast failures in my user-copy of the lock plugin. It significantly reduced the reset/retry storm, though the underlying fingerprint backend can still fail intermittently.
Expected behavior
After several rapid fingerprint device failures, stop fingerprint attempts for the rest of the current lock session (or use a long cooldown), while retaining password unlock. Reset this state after successful unlock.
Even if the underlying device failure belongs to fprintd/libfprint, the lock screen should avoid amplifying it into repeated rapid PAM retries and USB resets.
View raw text
### System details HONOR MagicBook Pro 14 2026; Omarchy 4.0.2-1; fprintd 1.94.5; libfprint 1.94.100 with an experimental SDCP fingerprint backend. ### What's wrong? ## What happened This occurs intermittently, not on every lock. The trigger I observed was: 1. Lock the session. 2. Let the lock screen automatically turn the display off. 3. Wake the display with the keyboard and try fingerprint unlock. On affected attempts, fingerprint authentication quickly fails with a device-integrity error. The lock screen keeps starting new fingerprint PAM sessions, and the kernel repeatedly resets the USB reader. Password unlock remains available. ## Why this looks like a lock-screen issue When the reader returns a fast transient failure, retrying fingerprint PAM every 250 ms appears to keep the device in an unusable state: each new attempt can trigger another USB reset before the reader has recovered. Stopping the rapid retries allows it to recover in most cases. ## Local mitigation I added a small backoff for fast failures in my user-copy of the lock plugin. It significantly reduced the reset/retry storm, though the underlying fingerprint backend can still fail intermittently. ## Expected behavior After several rapid fingerprint device failures, stop fingerprint attempts for the rest of the current lock session (or use a long cooldown), while retaining password unlock. Reset this state after successful unlock. Even if the underlying device failure belongs to fprintd/libfprint, the lock screen should avoid amplifying it into repeated rapid PAM retries and USB resets.
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
- Fixed bypr/11273· confirmed
- Fixed bypr/10653· 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.