Proof Portal

Sign in
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-5184GitHub issuePublicDecided· Out of scope

omarchy update asks for the sudo password on every AUR command

Reported by shawnyeager · filed Oct 6, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 2 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 update asks for the sudo password on every AUR commandrevision 1 · captured 2026-10-06 23:02 UTC via poll

System details

Dell XPS 14 DA14260, Intel Core Ultra X7 358H, Intel Arc B390 (Panther Lake, 8086:b080). omarchy-dev 4.0.0.r6721.g93b5d81-1. sudo 1.9.17p2.

What's wrong?

Thank you for #13323. One password now covers the update through mise, and that part is working.

AUR still drops that password and runs yay with sudo -N, so each sudo asks again and nothing is saved.

On 2026-10-06 at 13:39, one omarchy update asked once. That covered the cache prune, snapshot, signing keys, system packages, orphan removal, the shell restart, and mise. Updating two AUR packages, flea-bin and granola, then asked five more times. Those were yay's own sudo calls, after "Update AUR packages". The log is /tmp/omarchy-update.log.

One update should ask once. The password can be cleared when the update finishes. Happy to send a PR.

View raw text
### System details

Dell XPS 14 DA14260, Intel Core Ultra X7 358H, Intel Arc B390 (Panther Lake, 8086:b080). `omarchy-dev 4.0.0.r6721.g93b5d81-1`. sudo 1.9.17p2.

### What's wrong?

Thank you for #13323. One password now covers the update through mise, and that part is working.

AUR still drops that password and runs yay with `sudo -N`, so each sudo asks again and nothing is saved.

On 2026-10-06 at 13:39, one `omarchy update` asked once. That covered the cache prune, snapshot, signing keys, system packages, orphan removal, the shell restart, and mise. Updating two AUR packages, flea-bin and granola, then asked five more times. Those were yay's own sudo calls, after "Update AUR packages". The log is `/tmp/omarchy-update.log`.

One update should ask once. The password can be cleared when the update finishes. Happy to send a PR.

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 21:56 UTC