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-4682GitHub issuePublicFixed

omarchy-update hangs at migration 1787481315 when brave-origin is the daily browser (theme-set-browser blocks on brave that never exits)

Reported by sivaxreddy · filed Aug 25, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8158 (R-1486). 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 hangs at migration 1787481315 when brave-origin is the daily browser (theme-set-browser blocks on brave that never exits)revision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

omarchy update froze for over an hour right after the pacman phase, stuck at:

Running migration (1787481315)
Re-stage the current theme so an installed theme's code is dropped

Process tree showed the cause:

omarchy-migrate
└─ migrations/1787481315.sh
   └─ omarchy-theme-refresh
      └─ omarchy-theme-set eldritch
         └─ omarchy-theme-set-browser
            └─ /opt/brave-bin/brave --refresh-platform-policy --no-startup-window
               └─ full resident session: zygotes, gpu, network service, renderers — zero windows

refresh_running_browser brave brave in omarchy-theme-set-browser launched brave --refresh-platform-policy --no-startup-window, which never returned, blocking the migration and the entire update.

I daily-drive brave-origin (brave-origin-bin), so this stray plain-brave instance had no visible windows and the update just looked dead.

Expected

The refresh invocation should signal a running instance and exit promptly; the update should not hang on it indefinitely.

Workaround

Killing the spawned brave PID let the migration finish instantly and the update completed normally. No data lost (the stray process had no windows).

Steps to reproduce

  1. Have both brave-bin and brave-origin-bin installed; use brave-origin as the running browser.
  2. Run omarchy update.
  3. Update hangs at migration 1787481315 while omarchy-theme-set-browser waits on the never-exiting brave --refresh-platform-policy --no-startup-window child.

Suggested fix

Bound the call, e.g. timeout 10 "" --refresh-platform-policy --no-startup-window, or ensure flags that force exit after the policy handoff.

System

  • Omarchy 4.0.1-1
  • kernel 7.1.9-arch1-2
  • brave-bin 1:1.93.138-1, brave-origin-bin 1:1.93.138-1
View raw text
## What happened

`omarchy update` froze for over an hour right after the pacman phase, stuck at:

```
Running migration (1787481315)
Re-stage the current theme so an installed theme's code is dropped
```

Process tree showed the cause:

```
omarchy-migrate
└─ migrations/1787481315.sh
   └─ omarchy-theme-refresh
      └─ omarchy-theme-set eldritch
         └─ omarchy-theme-set-browser
            └─ /opt/brave-bin/brave --refresh-platform-policy --no-startup-window
               └─ full resident session: zygotes, gpu, network service, renderers — zero windows
```

`refresh_running_browser brave brave` in `omarchy-theme-set-browser` launched `brave --refresh-platform-policy --no-startup-window`, which never returned, blocking the migration and the entire update.

I daily-drive **brave-origin** (`brave-origin-bin`), so this stray plain-`brave` instance had no visible windows and the update just looked dead.

## Expected

The refresh invocation should signal a running instance and exit promptly; the update should not hang on it indefinitely.

## Workaround

Killing the spawned brave PID let the migration finish instantly and the update completed normally. No data lost (the stray process had no windows).

## Steps to reproduce

1. Have both `brave-bin` and `brave-origin-bin` installed; use brave-origin as the running browser.
2. Run `omarchy update`.
3. Update hangs at migration 1787481315 while omarchy-theme-set-browser waits on the never-exiting `brave --refresh-platform-policy --no-startup-window` child.

## Suggested fix

Bound the call, e.g. `timeout 10 "" --refresh-platform-policy --no-startup-window`, or ensure flags that force exit after the policy handoff.

## System

- Omarchy 4.0.1-1
- kernel 7.1.9-arch1-2
- brave-bin 1:1.93.138-1, brave-origin-bin 1:1.93.138-1

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

  • Fixed bypr/9423· confirmed

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.