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-1464GitHub issuePublicDecided· Out of scope

Omarchy 'omarchy update'

Reported by helioryn · filed Aug 25, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 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 'omarchy update'revision 1 · captured 2026-09-28 21:24 UTC via poll

System details

omarchy update crash — HP ProBook 450 G7 (Intel i3-10110U, x86_64, kernel 7.1.9)

Date: 2026-08-25 08:33:38

[1] Versions
omarchy 4.0.1-1
linux 7.1.9.arch1-2
kernel running: 7.1.8-arch1-3

[2] Is OMARCHY_PATH present in a normal (non-sudo) shell?
OMARCHY_PATH=/usr/share/omarchy
-> Under 'sudo' (default env_reset) sudo strips env vars it does not
whitelist, so OMARCHY_PATH is normally REMOVED for the update.

[3] Reproduce the crash: run the dev-check WITHOUT OMARCHY_PATH (as sudo does)
/usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
(exit above is from the crashed dev-check)
Expected output: /usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable

[4] The buggy script (line 7 + set -u will crash on unbound OMARCHY_PATH)
1 #!/bin/bash
2
3 # omarchy:summary=Update the active Omarchy dev checkout
4
5 set -euo pipefail
6
7 [[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0
8
9 if ! git -C "$OMARCHY_PATH" rev-parse --is-inside-work-tree >/dev/null 2>&1; then
10 echo "Error: OMARCHY_PATH is not a git checkout: $OMARCHY_PATH" >&2
11 exit 1
12 fi
13
14 upstream=$(git -C "$OMARCHY_PATH" rev-parse --abbrev-ref --symbolic-full-name '@{upstream}' 2>/dev/null || true)

[5] Confirm the fix: set OMARCHY_PATH and re-run (stock install should no-op)
exit=0 (exit 0 = check bypassed successfully)

[6] sudo env_keep: is OMARCHY_PATH whitelisted for sudo?
secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/bin, passwd_tries=10
Run as and Command-specific defaults for root:
Defaults!/usr/bin/visudo env_keep+="SUDO_EDITOR EDITOR VISUAL"

"omarchy update fails: OMARCHY_PATH: unbound variable (set -u + sudo env_reset)"

View raw text
### System details

omarchy update crash — HP ProBook 450 G7 (Intel i3-10110U, x86_64, kernel 7.1.9)

Date: 2026-08-25 08:33:38

[1] Versions
omarchy 4.0.1-1
linux 7.1.9.arch1-2
kernel running: 7.1.8-arch1-3

[2] Is OMARCHY_PATH present in a normal (non-sudo) shell?
    OMARCHY_PATH=/usr/share/omarchy
    -> Under 'sudo' (default env_reset) sudo strips env vars it does not
       whitelist, so OMARCHY_PATH is normally REMOVED for the update.

[3] Reproduce the crash: run the dev-check WITHOUT OMARCHY_PATH (as sudo does)
/usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
    (exit above is from the crashed dev-check)
    Expected output:  /usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable

[4] The buggy script (line 7 + set -u will crash on unbound OMARCHY_PATH)
     1	#!/bin/bash
     2	
     3	# omarchy:summary=Update the active Omarchy dev checkout
     4	
     5	set -euo pipefail
     6	
     7	[[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0
     8	
     9	if ! git -C "$OMARCHY_PATH" rev-parse --is-inside-work-tree >/dev/null 2>&1; then
    10	 echo "Error: OMARCHY_PATH is not a git checkout: $OMARCHY_PATH" >&2
    11	 exit 1
    12	fi
    13	
    14	upstream=$(git -C "$OMARCHY_PATH" rev-parse --abbrev-ref --symbolic-full-name '@{upstream}' 2>/dev/null || true)

[5] Confirm the fix: set OMARCHY_PATH and re-run (stock install should no-op)
    exit=0  (exit 0 = check bypassed successfully)

[6] sudo env_keep: is OMARCHY_PATH whitelisted for sudo?
    secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/bin, passwd_tries=10
Run as and Command-specific defaults for root:
    Defaults!/usr/bin/visudo env_keep+="SUDO_EDITOR EDITOR VISUAL"

        "omarchy update fails: OMARCHY_PATH: unbound variable (set -u + sudo env_reset)"

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 09:05 UTC