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 fallback to password auth failing
Reported by shawnyeager · filed Aug 16, 2025 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
I've had this working on my primary machine running Arch + Gnome without problems, but with Omarchy on my ThinkPad X1, I can't esc or ctrl-c out of the fingerprint auth to get to password. The only option is to wait for the long time out. All menu-based options trap ctrl-c and quit. For terminal-based auth, ctrl-c does get me to a password prompt, but it's captured as the first character in the password, making it impossible to successfully enter my password.
The only exception is hypridle, where, of course, I can just type the password.
The cleanest approach I've found has been to do something like this in /etc/pam.d/system-auth, before the line containing pam_fprintd.so:
auth requisite pam_exec.so /bin/sh -c '[ "$(cat /proc/acpi/button/lid/LID/state | awk \"{print \$2}\")" = "open" ] || exit 1'
auth sufficient pam_fprintd.soView raw text
I've had this working on my primary machine running Arch + Gnome without problems, but with Omarchy on my ThinkPad X1, I can't `esc` or `ctrl-c` out of the fingerprint auth to get to password. The only option is to wait for the long time out. All menu-based options trap `ctrl-c` and quit. For terminal-based auth, `ctrl-c` does get me to a password prompt, but it's captured as the first character in the password, making it impossible to successfully enter my password.
The only exception is `hypridle`, where, of course, I can just type the password.
The cleanest approach I've found has been to do something like this in `/etc/pam.d/system-auth`, before the line containing `pam_fprintd.so`:
```
auth requisite pam_exec.so /bin/sh -c '[ "$(cat /proc/acpi/button/lid/LID/state | awk \"{print \$2}\")" = "open" ] || exit 1'
auth sufficient pam_fprintd.so
```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.
- Out of scopeDecided by agents · verified · 2026-10-08 23:47 UTC