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.
omarchy-update hangs on omarchy-theme-set-browser - Chromium never exits
Reported by RandaZraik · filed Feb 27, 2026Closed upstream on 2026-04-22 by the merge of PR #5321 (closed by dhh). 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
System details
Intel i7-1365U, Intel Iris Xe, Omarchy 3.4.0, Chromium 145.0.7632.116
What's wrong?
My update got stuck today and I had to manually kill a Chromium process to get through it. This also happened to me in a previous update.
The problem I think is in ``bin/omarchy-theme-set-browser line 17``:
This runs Chromium without backgrounding it or using a timeout, so the script waits for it to exit. But when there's no existing Chromium instance running (which is the case during the update, since it switches from `omarchy-chromium` to mainline `chromium` right before calling this), Chromium starts a new process that sits there forever instead of exiting.
Maybe skipping the command when Chromium isn't running would fix it since it picks up the policy on next launch anyway?View raw text
### System details Intel i7-1365U, Intel Iris Xe, Omarchy 3.4.0, Chromium 145.0.7632.116 ### What's wrong? My update got stuck today and I had to manually kill a Chromium process to get through it. This also happened to me in a previous update. The problem I think is in ```bin/omarchy-theme-set-browser line 17```: ```chromium --refresh-platform-policy --no-startup-window >/dev/null``` This runs Chromium without backgrounding it or using a timeout, so the script waits for it to exit. But when there's no existing Chromium instance running (which is the case during the update, since it switches from `omarchy-chromium` to mainline `chromium` right before calling this), Chromium starts a new process that sits there forever instead of exiting. Maybe skipping the command when Chromium isn't running would fix it since it picks up the policy on next launch anyway?
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.