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.
Lockouts on sudo still happen after 3 attempts
Reported by dhh · filed Aug 11, 2025Closed upstream on 2025-08-22 by its own reporter dhh. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
I'd tried to increase the lockout count to 10, but seems like that's not applying to sudo. If you accumulate 3 fails, you'll get logged out, and then you need to do the "su -; faillock --reset --user dhh" dance. That's a hassle! We need to find out why this isn't applying. And also find out how to get it reset such that a single successful sudo resets the failure counter.
View raw text
I'd tried to increase the lockout count to 10, but seems like that's not applying to sudo. If you accumulate 3 fails, you'll get logged out, and then you need to do the "su -; faillock --reset --user dhh" dance. That's a hassle! We need to find out why this isn't applying. And also find out how to get it reset such that a single successful sudo resets the failure counter.
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.