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

omarchy-update-dev fails with unbound variable OMARCHY_PATH under sudo

Reported by henriquemeira · filed Sep 10, 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 fails with unbound variable OMARCHY_PATH under sudorevision 1 · captured 2026-10-04 12:10 UTC via poll

Description

When running sudo omarchy update, the update fails with:

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

Cause

omarchy-update-dev uses set -euo pipefail (nounset) but references $OMARCHY_PATH without a default value on line 7:

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

When running via sudo, the environment is reset and OMARCHY_PATH is not inherited from the user shell, causing the nounset error.

Fix

Use a default parameter expansion:

[[ ${OMARCHY_PATH:-/usr/share/omarchy} != "/usr/share/omarchy" ]] || exit 0

This defaults to /usr/share/omarchy when unset, which matches the intended early-exit behavior for non-dev installs.

Environment

  • Omarchy version: 4.0.2-1
  • Sudo version: 1.9.17p2
View raw text
## Description

When running `sudo omarchy update`, the update fails with:

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

## Cause

`omarchy-update-dev` uses `set -euo pipefail` (nounset) but references `$OMARCHY_PATH` without a default value on line 7:

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

When running via `sudo`, the environment is reset and `OMARCHY_PATH` is not inherited from the user shell, causing the nounset error.

## Fix

Use a default parameter expansion:

```bash
[[ ${OMARCHY_PATH:-/usr/share/omarchy} != "/usr/share/omarchy" ]] || exit 0
```

This defaults to `/usr/share/omarchy` when unset, which matches the intended early-exit behavior for non-dev installs.

## Environment

- Omarchy version: 4.0.2-1
- Sudo version: 1.9.17p2

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.