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

omarchy update fails with "unsafe Omarchy update inhibitor state path" on non-English locales

Reported by higorhgon · filed Sep 30, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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 update fails with "unsafe Omarchy update inhibitor state path" on non-English localesrevision 1 · captured 2026-09-30 17:06 UTC via poll

System

  • Omarchy: 4.0.0.r6689.gb421b1b-1 (omarchy-dev)
  • Locale: LANG=pt_BR.UTF-8
  • Kernel: 7.2.5-4-omarchy

What happened

omarchy update aborts right after "Create system snapshot":

Refusing to use an unsafe Omarchy update inhibitor state path.
Something went wrong during the update!

Expected

The update proceeds. /run/user/1000 is drwx------ 1000:1000 and /, /run, /run/user are root-owned and not group/other-writable, so the path is safe.

Cause

bin/omarchy-update-stay-awake, in root_owned_parent_chain() (line ~71):

read -r owner mode type < <(/usr/bin/stat -Lc '%u %a %F' -- "$parent") || return 1
[[ $owner == 0 && $type == "directory" ]] || return 1

stat %F is localized. With pt_BR.UTF-8 it prints diretório, so the comparison fails for / and the script calls fail_state_boundary. Any locale where the word for "directory" differs from English is affected; multi-word translations would also be split by read.

Reproduction

omarchy-update-stay-awake stop          # LANG=pt_BR.UTF-8 -> error, exit 1
LC_ALL=C omarchy-update-stay-awake stop # exit 0

Suggested fix

The same function already checks [[ -d $parent && ! -L $parent ]] a few lines above, so %F is redundant. Either drop type from the stat format and the comparison, or run stat with LC_ALL=C.

Workaround

LC_ALL=C omarchy update

View raw text
## System
- Omarchy: 4.0.0.r6689.gb421b1b-1 (omarchy-dev)
- Locale: `LANG=pt_BR.UTF-8`
- Kernel: 7.2.5-4-omarchy

## What happened
`omarchy update` aborts right after "Create system snapshot":

```
Refusing to use an unsafe Omarchy update inhibitor state path.
Something went wrong during the update!
```

## Expected
The update proceeds. `/run/user/1000` is `drwx------ 1000:1000` and `/`, `/run`, `/run/user` are root-owned and not group/other-writable, so the path is safe.

## Cause
`bin/omarchy-update-stay-awake`, in `root_owned_parent_chain()` (line ~71):

```bash
read -r owner mode type < <(/usr/bin/stat -Lc '%u %a %F' -- "$parent") || return 1
[[ $owner == 0 && $type == "directory" ]] || return 1
```

`stat %F` is localized. With `pt_BR.UTF-8` it prints `diretório`, so the comparison fails for `/` and the script calls `fail_state_boundary`. Any locale where the word for "directory" differs from English is affected; multi-word translations would also be split by `read`.

## Reproduction
```bash
omarchy-update-stay-awake stop          # LANG=pt_BR.UTF-8 -> error, exit 1
LC_ALL=C omarchy-update-stay-awake stop # exit 0
```

## Suggested fix
The same function already checks `[[ -d $parent && ! -L $parent ]]` a few lines above, so `%F` is redundant. Either drop `type` from the `stat` format and the comparison, or run `stat` with `LC_ALL=C`.

## Workaround
`LC_ALL=C omarchy update`

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 20:22 UTC