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.
omarchy update aborts: OMARCHY_PATH: unbound variable in omarchy-update-dev
Reported by Twistedw1ll · filed Sep 22, 2026Closed upstream on 2026-10-12 by the bot omarchybot, as a duplicate (target not recorded).
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
Bug description
omarchy update aborts with:
/usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
Expected behavior
If OMARCHY_PATH is unset, the script should fall back to the packaged default (as other omarchy scripts do, e.g. env-bootstrap: : "${OMARCHY_PATH:=/usr/share/omarchy}").
Steps to reproduce
Run omarchy-update-dev from an environment without OMARCHY_PATH set:
env -i bash -c '/usr/bin/omarchy-update-dev'
# -> /usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
This happens when omarchy update is launched from a stripped environment (e.g. sudo omarchy update, cron/timer, non-bash shell). The same command runs fine from a normal login shell, where ~/.bashrc / /etc/profile.d/omarchy.sh export it.
Root cause
/usr/bin/omarchy-update-dev runs under set -euo pipefail and reads $OMARCHY_PATH directly on line 7. Unlike env-bootstrap, it never defaults the variable:
[[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0
Suggested fix: [[ ${OMARCHY_PATH:-/usr/share/omarchy} != "/usr/share/omarchy" ]] || exit 0
System details
- Omarchy: 4.0.4-1
- Kernel: 7.2.5-3-omarchy (x86_64)
- CPU: AMD Ryzen 7 5800XT
- GPU: NVIDIA (vendor 0x10de, device 0x2489)
View raw text
## Bug description
`omarchy update` aborts with:
/usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
## Expected behavior
If OMARCHY_PATH is unset, the script should fall back to the packaged default (as other omarchy scripts do, e.g. `env-bootstrap`: `: "${OMARCHY_PATH:=/usr/share/omarchy}"`).
## Steps to reproduce
Run omarchy-update-dev from an environment without OMARCHY_PATH set:
env -i bash -c '/usr/bin/omarchy-update-dev'
# -> /usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
This happens when `omarchy update` is launched from a stripped environment (e.g. `sudo omarchy update`, cron/timer, non-bash shell). The same command runs fine from a normal login shell, where `~/.bashrc` / `/etc/profile.d/omarchy.sh` export it.
## Root cause
`/usr/bin/omarchy-update-dev` runs under `set -euo pipefail` and reads `$OMARCHY_PATH` directly on line 7. Unlike `env-bootstrap`, it never defaults the variable:
[[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0
Suggested fix: `[[ ${OMARCHY_PATH:-/usr/share/omarchy} != "/usr/share/omarchy" ]] || exit 0`
## System details
- Omarchy: 4.0.4-1
- Kernel: 7.2.5-3-omarchy (x86_64)
- CPU: AMD Ryzen 7 5800XT
- GPU: NVIDIA (vendor 0x10de, device 0x2489)
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 17:05 UTC