Proof Portal

Sign in
Project overview

Omarchy

ProbeLabsviewing a historical run

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.

Viewing historical run 033e0d5Oct 2, 2026, 07:36 PMpr/13012Back to current
Back to findings
Known issueKI-MENU-SELECT-POLL-DEADLOCK

omarchy-menu-select hangs forever when the summoned menu dies before writing done_file

OpenReviewedMedium

Medium-severity issue, currently open.

Description

The issue as recorded.

The done_file poll in bin/omarchy-menu-select (lines 93-95) has no deadline and no peer-liveness probe. If the menu process dies after a successful summon IPC, nothing writes the done file. The script loops forever and hangs every synchronous caller. The protocol covers user cancel but not peer death. Reproduced live on 2026-09-23: an external 3s timeout killed the waiting script. No requirement pins a bounded wait, so the defect had no contract to violate.

Affected requirements

The requirement(s) this issue violates — click through to the spec.

SW-REQ-260922-Q6ZSSW-REQ-260922-9ABDSW-REQ-260922-HR29SW-REQ-260922-KRBHSW-REQ-260922-MP00SW-REQ-260922-MH9BSW-REQ-260922-SWFT

Severity, explained

Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).

MediumRated severity — the impact if this issue is exploited or hit.
why this rating
Reproducer-confirmed
Security classification
Not a security surface
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.

Known issue reproducedprofileknown_issue_reproducerprovesSW-REQ-260922-Q6ZS
Reproducer test
Run it yourself
/bin/bash test/shell.d/menu-select-poll-deadlock-repro.sh
Covers (2)
Last run Sep 30, 2026, 9:01 PM

Reproduction steps

Technical steps for your engineers to confirm the issue by hand.

/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.

No authoredcode links reach these requirements in this historical reconstruction. Automatically derived code links aren't reconstructible for past runs, so implementing code may have existed without an authored trace.

Tracing blast radius…

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.

Sign in to discuss this with the proof team.Sign in