Proof Portal
Omarchy
ProbeLabsviewing a historical runA 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-menu-select hangs forever when the summoned menu dies before writing done_file
Medium-severity issue, currently open.
Description
The issue as recorded.
The done_file poll in bin/omarchy-menu-select (lines 93-95) is unbounded: while [[ ! -e $done_file ]]; do sleep 0.05; done carries no deadline, no peer-liveness probe, and no signal beyond the EXIT trap. If the menu process dies after the summon IPC succeeds (Quickshell crash, compositor restart), nothing ever writes the done file and the script loops forever, hanging every caller that invokes it synchronously. The protocol covers user cancel (the cancel path writes done_file) but not peer death. Reproduced live: with omarchy-shell stubbed to exit 0 and nothing writing the done file, the script was killed by an external 3s timeout (repro exits 1 = defect present). The spec gap rides with it: no requirement pins a bounded wait for the poll, so the defect had no contract to violate — the negative-state half of the dmenu protocol was never specified.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Reproducer-confirmed
- CVE surface
- None
Where it is
The code the issue lives in — peek the affected function inline to see it in context.
- bin/omarchy-menu-select (dmenu select protocol)
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
/opt/homebrew/bin/bash test/shell.d/menu-select-poll-deadlock-repro.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
/opt/homebrew/bin/bash test/shell.d/menu-select-poll-deadlock-repro.sh
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
Touch this finding and you re-check 1 requirements · 1 code files · 1 tests.
- omarchy-menu-select
- menu-dmenu-test.sh
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- test/shell.d/menu-select-poll-deadlock-repro.sh
- proof/evidence/ki-menu-select-poll-deadlock.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.