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.
Keep first run pending when user finalization fails
Reported by maralcbr · filed Oct 2, 2026 · 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
omarchy-provision-first-run runs omarchy-provision-user "${finalize_user_args[@]}" || true before its other steps, so a failed user finalization is dropped. If the later steps succeed, first run is marked done, and the user's finalization is never retried at the next login.
This matters most on image installs (Apple Silicon today), where first boot creates and finalizes the owner's account. It applies to every install that finalizes a user at first run.
omacom/omarchy#13362 carried a fix: finalization was logged and counted like any other first-run step, so a failure left first run pending and retryable, with a test in test/shell.d/first-run-test.sh. d0b94d98c returned it to quattro's behavior so it can land on its own merits. That commit's diff of bin/omarchy-provision-first-run and test/shell.d/first-run-test.sh holds the change to bring back.
View raw text
`omarchy-provision-first-run` runs `omarchy-provision-user "${finalize_user_args[@]}" || true` before its other steps, so a failed user finalization is dropped. If the later steps succeed, first run is marked done, and the user's finalization is never retried at the next login.
This matters most on image installs (Apple Silicon today), where first boot creates and finalizes the owner's account. It applies to every install that finalizes a user at first run.
omacom/omarchy#13362 carried a fix: finalization was logged and counted like any other first-run step, so a failure left first run pending and retryable, with a test in `test/shell.d/first-run-test.sh`. d0b94d98c returned it to quattro's behavior so it can land on its own merits. That commit's diff of `bin/omarchy-provision-first-run` and `test/shell.d/first-run-test.sh` holds the change to bring back.
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-09 20:50 UTC