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.
sudo omarchy update aborts with "OMARCHY_PATH: unbound variable" in omarchy-update-dev
Reported by MaurizioFaeddaDev · filed Sep 3, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8239 (R-1464). GitHub close reason: completed.
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
sudo omarchy update aborts right after the system snapshot with:
Prune package cache
==> no candidate packages found for pruning
Create system snapshot
Snapshots can be selected during boot.
/usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
Something went wrong during the update!The update never reaches omarchy-update-system-pkgs, so no packages are upgraded.
What happens
omarchy-update-dev runs with set -euo pipefail and its first check dereferences OMARCHY_PATH:
set -euo pipefail
[[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0 # line 7OMARCHY_PATH is normally exported by /etc/profile.d/omarchy.sh (login shells) and the uwsm session env, but `sudo` resets the environment (env_reset), so when the update runs as root the variable is unset. Under set -u the unbound reference kills the script, the parent omarchy-update ERR trap fires, and the whole update is aborted.
The script clearly intends to be a no-op on stock installs (it exits when the path points at /usr/share/omarchy), it just doesn't handle the case where the variable is not set at all.
Steps to reproduce
- On a stock (non dev-linked) Omarchy install, from a normal terminal:
sudo omarchy update
2. Update proceeds through cache prune + snapper snapshot, then dies at omarchy-update-dev with OMARCHY_PATH: unbound variable.
Expected
The update should continue normally. omarchy-update-dev should treat an unset OMARCHY_PATH as the stock install location.
Suggested fix
[[ ${OMARCHY_PATH:-/usr/share/omarchy} != "/usr/share/omarchy" ]] || exit 0(Alternatively, omarchy-update could set OMARCHY_PATH=${OMARCHY_PATH:-/usr/share/omarchy} before calling into sub-scripts.)
Workaround
sudo env OMARCHY_PATH=/usr/share/omarchy omarchy updateSystem details
- Omarchy package:
omarchy 4.0.2-1,aether 4.29.8-1 - Kernel: 7.1.9-arch1-2
- Hyprland 0.56.2
- Hardware: HUAWEI KPL-W0X laptop, AMD Ryzen 5 2500U, amdgpu
Full diagnostic output is available at /tmp/omarchy-debug.log (can attach on request).
View raw text
### Summary
`sudo omarchy update` aborts right after the system snapshot with:
```
Prune package cache
==> no candidate packages found for pruning
Create system snapshot
Snapshots can be selected during boot.
/usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable
Something went wrong during the update!
```
The update never reaches `omarchy-update-system-pkgs`, so no packages are upgraded.
### What happens
`omarchy-update-dev` runs with `set -euo pipefail` and its first check dereferences `OMARCHY_PATH`:
```bash
set -euo pipefail
[[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0 # line 7
```
`OMARCHY_PATH` is normally exported by `/etc/profile.d/omarchy.sh` (login shells) and the uwsm session env, but **`sudo` resets the environment** (`env_reset`), so when the update runs as root the variable is unset. Under `set -u` the unbound reference kills the script, the parent `omarchy-update` ERR trap fires, and the whole update is aborted.
The script clearly intends to be a no-op on stock installs (it exits when the path points at `/usr/share/omarchy`), it just doesn't handle the case where the variable is not set at all.
### Steps to reproduce
1. On a stock (non dev-linked) Omarchy install, from a normal terminal:
`sudo omarchy update`
2. Update proceeds through cache prune + snapper snapshot, then dies at `omarchy-update-dev` with `OMARCHY_PATH: unbound variable`.
### Expected
The update should continue normally. `omarchy-update-dev` should treat an unset `OMARCHY_PATH` as the stock install location.
### Suggested fix
```bash
[[ ${OMARCHY_PATH:-/usr/share/omarchy} != "/usr/share/omarchy" ]] || exit 0
```
(Alternatively, `omarchy-update` could set `OMARCHY_PATH=${OMARCHY_PATH:-/usr/share/omarchy}` before calling into sub-scripts.)
### Workaround
```bash
sudo env OMARCHY_PATH=/usr/share/omarchy omarchy update
```
### System details
- Omarchy package: `omarchy 4.0.2-1`, `aether 4.29.8-1`
- Kernel: 7.1.9-arch1-2
- Hyprland 0.56.2
- Hardware: HUAWEI KPL-W0X laptop, AMD Ryzen 5 2500U, amdgpu
Full diagnostic output is available at `/tmp/omarchy-debug.log` (can attach on request).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.