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-4698GitHub issuePublicReceived

omarchy-update-dev crashes with "unbound variable" on $OMARCHY_PATH under sudo

Reported by edhcah · filed Aug 26, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8239 (R-1464). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

omarchy-update-dev crashes with "unbound variable" on $OMARCHY_PATH under sudorevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

sudo omarchy update fails partway through with:

/usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable

Steps to reproduce

  1. Run sudo omarchy update on a standard (non-dev-checkout) Omarchy install.
  2. It fails during the dev-checkout-update step.

Cause

omarchy-update-dev runs under set -euo pipefail and references
$OMARCHY_PATH directly on line 7:

[[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0

without a fallback default. Every other Omarchy script sets one
(: "${OMARCHY_PATH:=/usr/share/omarchy}" — see e.g.
default/bash/rc), but this one doesn't. Since sudo's default
env_reset strips OMARCHY_PATH from the environment before the
update script runs as root, the variable is unset when
omarchy-update-dev (invoked from omarchy-update) checks it, and
set -u turns that into a fatal error.

Expected

Same fallback default as the rest of the codebase, e.g.:

: "${OMARCHY_PATH:=/usr/share/omarchy}"

added near the top of omarchy-update-dev (or OMARCHY_PATH exported
explicitly by omarchy-update before invoking it).

Workaround

sudo OMARCHY_PATH=/usr/share/omarchy omarchy update

System

  • Omarchy 4.0.1-1
  • Kernel 7.1.9-arch1-2
  • Dell Latitude 7450, Intel Core Ultra 7 165U
  • sudoers: default env_reset (no OMARCHY_PATH in env_keep)
View raw text
### What happened
`sudo omarchy update` fails partway through with:

    /usr/bin/omarchy-update-dev: line 7: OMARCHY_PATH: unbound variable

### Steps to reproduce
1. Run `sudo omarchy update` on a standard (non-dev-checkout) Omarchy install.
2. It fails during the dev-checkout-update step.

### Cause
`omarchy-update-dev` runs under `set -euo pipefail` and references
`$OMARCHY_PATH` directly on line 7:

    [[ $OMARCHY_PATH != "/usr/share/omarchy" ]] || exit 0

without a fallback default. Every other Omarchy script sets one
(`: "${OMARCHY_PATH:=/usr/share/omarchy}"` — see e.g.
default/bash/rc), but this one doesn't. Since sudo's default
`env_reset` strips OMARCHY_PATH from the environment before the
update script runs as root, the variable is unset when
omarchy-update-dev (invoked from omarchy-update) checks it, and
`set -u` turns that into a fatal error.

### Expected
Same fallback default as the rest of the codebase, e.g.:

    : "${OMARCHY_PATH:=/usr/share/omarchy}"

added near the top of omarchy-update-dev (or OMARCHY_PATH exported
explicitly by omarchy-update before invoking it).

### Workaround
    sudo OMARCHY_PATH=/usr/share/omarchy omarchy update

### System
- Omarchy 4.0.1-1
- Kernel 7.1.9-arch1-2
- Dell Latitude 7450, Intel Core Ultra 7 165U
- sudoers: default `env_reset` (no OMARCHY_PATH in env_keep)

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.