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.
Edge: omarchy-settings-dev (c3e67f5) lags omarchy-dev (7b336b1), missing default/omarchy/sudo-no-update/sudo, so omarchy update always fails
Reported by paralyses2193 · filed Sep 26, 2026Closed upstream on 2026-09-26 by its own reporter paralyses2193. 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
Summary
omarchy-dev 4.0.0.r2304.g7b336b1-1 does not ship default/omarchy/sudo-no-update/sudo, but the scripts in the same package require it. As a result, every omarchy update stops right at the start with:
The command-scoped sudo wrapper is missing.Evidence
- The file exists in the source at the package's commit:
default/omarchy/sudo-no-update/sudoat7b336b1. - It is not in the package:
bsdtar -tf omarchy-dev-4.0.0.r2304.g7b336b1-1-x86_64.pkg.tar.zst | grep no-update prints nothing, and pacman -Ql omarchy-dev | grep no-update prints nothing.
- /usr/bin/omarchy-update (line 28) and /usr/bin/omarchy-update-stay-awake (line 22) call omarchy_security_enable_no_update_sudo. In /usr/bin/omarchy-security-functions, that function checks $OMARCHY_PATH/default/omarchy/sudo-no-update/sudo and returns 1 when the file is missing.
- The previous package, 4.0.0.r2186.gee8ebf6-1, also lacked the file, but its scripts never called that function.
How it surfaced
- On r2186, I ran
omarchy update. The system-packages step upgradedomarchy-devto r2304 in the middle of the run. Migrations, AUR and mise all finished. - The old
omarchy-updatethen called the newomarchy-update-stay-awake stop. That call failed with the message above (printed twice: once from the explicit call, once from the EXIT trap). The update ended with "Something went wrong during the update!" - Side effect: the root
systemd-inhibit --what=sleep:idle --who=omarchy-update ... sleep infinityprocess was left running, so the machine would not sleep or idle-lock until it was killed by hand. - Every later
omarchy updatefails immediately, because the new entrypoint needs the wrapper before it does anything else.
Expected
The package installs /usr/share/omarchy/default/omarchy/sudo-no-update/sudo as an executable. Separately, when the stay-awake stop fails, the update should still release the inhibitor it started.
Environment
- Channel: dev (
omarchy-dev 4.0.0.r2304.g7b336b1-1) - sudo supports
-N(the--no-updatecheck passes; the failing check is the missing file)
View raw text
## Summary `omarchy-dev 4.0.0.r2304.g7b336b1-1` does not ship `default/omarchy/sudo-no-update/sudo`, but the scripts in the same package require it. As a result, every `omarchy update` stops right at the start with: ``` The command-scoped sudo wrapper is missing. ``` ## Evidence - The file exists in the source at the package's commit: `default/omarchy/sudo-no-update/sudo` at `7b336b1`. - It is not in the package: `bsdtar -tf omarchy-dev-4.0.0.r2304.g7b336b1-1-x86_64.pkg.tar.zst | grep no-update` prints nothing, and `pacman -Ql omarchy-dev | grep no-update` prints nothing. - `/usr/bin/omarchy-update` (line 28) and `/usr/bin/omarchy-update-stay-awake` (line 22) call `omarchy_security_enable_no_update_sudo`. In `/usr/bin/omarchy-security-functions`, that function checks `$OMARCHY_PATH/default/omarchy/sudo-no-update/sudo` and returns 1 when the file is missing. - The previous package, `4.0.0.r2186.gee8ebf6-1`, also lacked the file, but its scripts never called that function. ## How it surfaced 1. On r2186, I ran `omarchy update`. The system-packages step upgraded `omarchy-dev` to r2304 in the middle of the run. Migrations, AUR and mise all finished. 2. The old `omarchy-update` then called the new `omarchy-update-stay-awake stop`. That call failed with the message above (printed twice: once from the explicit call, once from the EXIT trap). The update ended with "Something went wrong during the update!" 3. Side effect: the root `systemd-inhibit --what=sleep:idle --who=omarchy-update ... sleep infinity` process was left running, so the machine would not sleep or idle-lock until it was killed by hand. 4. Every later `omarchy update` fails immediately, because the new entrypoint needs the wrapper before it does anything else. ## Expected The package installs `/usr/share/omarchy/default/omarchy/sudo-no-update/sudo` as an executable. Separately, when the stay-awake stop fails, the update should still release the inhibitor it started. ## Environment - Channel: dev (`omarchy-dev 4.0.0.r2304.g7b336b1-1`) - sudo supports `-N` (the `--no-update` check passes; the failing check is the missing file)
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.