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

omarchy-menu-select waiter never exits if the shell drops the menu

Reported by undergroundpost · filed Oct 7, 2026 · open at source

Open at source
Decided: Duplicate — 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?
AreaIn the audited areamenu· 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-menu-select waiter never exits if the shell drops the menurevision 1 · captured 2026-10-07 00:09 UTC via poll

System details

Framework Laptop 13, Ryzen AI 9 HX 370 (Radeon 890M), Omarchy 4.0.4

What's wrong?

omarchy-menu-select waits for the menu by polling for its done file (bin/omarchy-menu-select lines 91-93, sleep 0.05) with no timeout. If the shell restarts or drops the menu before writing that file, the waiter never exits.

I found five orphaned omarchy-menu-select Keybindings waiters, the oldest about 11 hours old. Each used about 0.65% CPU and together they forked about 100 sleep processes per second.

Steps:

  1. Open the keybindings menu (SUPER+K).
  2. Run omarchy restart shell while it is open.
  3. pgrep -fa omarchy-menu-select shows the waiter still running.

Possible fixes: add a timeout, or exit when the shell instance that owns the menu goes away. Possibly related to #13072.

View raw text
### System details

Framework Laptop 13, Ryzen AI 9 HX 370 (Radeon 890M), Omarchy 4.0.4

### What's wrong?

`omarchy-menu-select` waits for the menu by polling for its done file (`bin/omarchy-menu-select` lines 91-93, `sleep 0.05`) with no timeout. If the shell restarts or drops the menu before writing that file, the waiter never exits.

I found five orphaned `omarchy-menu-select Keybindings` waiters, the oldest about 11 hours old. Each used about 0.65% CPU and together they forked about 100 `sleep` processes per second.

Steps:

1. Open the keybindings menu (SUPER+K).
2. Run `omarchy restart shell` while it is open.
3. `pgrep -fa omarchy-menu-select` shows the waiter still running.

Possible fixes: add a timeout, or exit when the shell instance that owns the menu goes away. Possibly related to #13072.

Same defect, also reported as

1 other report describesomarchy-menu-select hangs forever when the summoned menu dies before writing done_file KI-MENU-SELECT-POLL-DEADLOCK

Earliest report: R-1570 (filed Aug 22, 2026).

  1. Aug 22, 2026Superseding a pending omarchy-menu-select leaks a permanent 20 fork/sec busy-wait loop R-1570

    Open upstream.

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

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.