Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-41GitHub issuePublicDecided· Out of scope

omarchy edge still ships r2304 — sudo fix from #13323 not packaged yet

Reported by nightdevil00 · filed Sep 27, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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 edge still ships r2304 — sudo fix from #13323 not packaged yetrevision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

Filed #13415 on 2026-09-27 against omarchy update asking for the sudo password repeatedly during a channel switch. That issue's own description says the fix landed in #13323 ("Ask for the sudo password once per omarchy update"), merged 2026-09-26, and that "Channel switching still authorizes its own steps command by command" — so the remaining gap is known and deferred.

I rebooted and ran omarchy update twice (output2.log, output3.log) to verify the fix reached my machine. It hasn't. Both runs still prompt 9 times for the same steps #13323 was supposed to collapse to one:

Prune package cache           → sudo
Create system snapshot        → sudo ×4
Update Arch signing keys      → sudo ×2
Update system packages        → sudo

pacman -Si omarchy-dev still reports 4.0.0.r2304.g7b336b1-1 — the pre-fix build. The edge repo hasn't been rebuilt with the merged PR.

Expected

Edge should carry the fix within a build or two of merge, since the whole point of the PR was to stop asking for the password repeatedly. A user switching channel today hits the old behavior for the channel switch and for the subsequent omarchy update — two separate flows, both unfixed on edge.

Also

Once the fix lands, the remaining ~3 prompts from omarchy-channel-set's own steps (refresh-pacman ×2, pacman -S) are worth a follow-up too — #13323's description names this explicitly. I can reopen #13415 with that scope once the packaged fix is verified, or split it.

System details

Omarchy        4.0.0.r2304.g7b336b1-1 (edge, still pre-fix)
kernel         7.2.5-4-omarchy running, installed by the switch
log            output2.log, output3.log — 9 prompts each run
date           2026-09-27
View raw text
## What happened

Filed #13415 on 2026-09-27 against `omarchy update` asking for the sudo password repeatedly during a channel switch. That issue's own description says the fix landed in #13323 ("Ask for the sudo password once per omarchy update"), merged 2026-09-26, and that *"Channel switching still authorizes its own steps command by command"* — so the remaining gap is known and deferred.

I rebooted and ran `omarchy update` twice (output2.log, output3.log) to verify the fix reached my machine. It hasn't. Both runs still prompt 9 times for the same steps #13323 was supposed to collapse to one:

```
Prune package cache           → sudo
Create system snapshot        → sudo ×4
Update Arch signing keys      → sudo ×2
Update system packages        → sudo
```

`pacman -Si omarchy-dev` still reports `4.0.0.r2304.g7b336b1-1` — the pre-fix build. The edge repo hasn't been rebuilt with the merged PR.

## Expected

Edge should carry the fix within a build or two of merge, since the whole point of the PR was to stop asking for the password repeatedly. A user switching channel today hits the old behavior for the channel switch *and* for the subsequent `omarchy update` — two separate flows, both unfixed on edge.

## Also

Once the fix lands, the remaining ~3 prompts from `omarchy-channel-set`'s own steps (refresh-pacman ×2, pacman -S) are worth a follow-up too — #13323's description names this explicitly. I can reopen #13415 with that scope once the packaged fix is verified, or split it.

## System details

```
Omarchy        4.0.0.r2304.g7b336b1-1 (edge, still pre-fix)
kernel         7.2.5-4-omarchy running, installed by the switch
log            output2.log, output3.log — 9 prompts each run
date           2026-09-27
```

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 19:25 UTC