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.

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

Fix status

Whether this is simply open, open with a fix proposed, or already fixed upstream — and the pull request / issue that tracks it.

PR #9031

A fix has been proposed upstream — follow the pull request or issue below to track it.

Vendor
omacom/omarchy
Channel
issue_tracker
Reported in
View pull request / issue
Reference
#9031
Reported
2026-08-29
Reported by
human:github/markvogel
Vendor response
Fix In Progress view
Response received
2026-10-04

Reviewed Dec 23, 2026

Reported → Fix proposed → Fixed reflect the upstream disclosure lifecycle: the issue has been reported to the vendor, a pull request or issue is open to fix it, or a released fix is available.

Reported upstream as

2 reports in the inbox describe this issue.

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 Oct 4, 2026, 9:47 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.

Tracing blast radius…

Touch this finding and you re-check 7 requirements · 6 code files · 5 tests.

Requirements (7)
SW-REQ-260922-Q6ZSSW-REQ-260922-9ABDSW-REQ-260922-HR29SW-REQ-260922-KRBHSW-REQ-260922-MP00SW-REQ-260922-MH9BSW-REQ-260922-SWFT
Code files (6)
  • omarchy-menu-select
  • omarchy-menu-input
  • omarchy-menu-file
  • omarchy-menu-plugin
  • omarchy-menu-images
  • omarchy-menu-timezone
Tests (5)
  • menu-dmenu-test.sh
  • menu-file-test.sh
  • menu-plugin-test.sh
  • menu-images-test.sh
  • menu-timezone-test.sh

Per-requirement evidence

For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.

SW-REQ-260922-Q6ZS
Implementing code (1)
  • bin/omarchy-menu-select
Tests & evidence (1)
  • test/shell.d/menu-dmenu-test.sh
Proof obligations (2)
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)
input_domain

A parser, reader, or configuration loader states its accepted input domain at the byte level and what happens for each partition of it.

  • ✓nominal (required) — test/shell.d/menu-dmenu-test.sh:140, test/shell.d/menu-dmenu-test.sh:145, test/shell.d/menu-dmenu-test.sh:150, test/shell.d/menu-dmenu-test.sh:155, test/shell.d/menu-dmenu-test.sh:161
  • ✓negative — test/shell.d/menu-dmenu-test.sh:165, test/shell.d/menu-dmenu-test.sh:171
SW-REQ-260922-9ABD
Implementing code (2)
  • bin/omarchy-menu-input
  • bin/omarchy-menu-select
Tests & evidence (1)
  • test/shell.d/menu-dmenu-test.sh
Proof obligations (1)
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)
SW-REQ-260922-HR29
Implementing code (1)
  • bin/omarchy-menu-file
Tests & evidence (1)
  • test/shell.d/menu-file-test.sh
Proof obligations (1)
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)
SW-REQ-260922-KRBH
Implementing code (1)
  • bin/omarchy-menu-plugin
Tests & evidence (1)
  • test/shell.d/menu-plugin-test.sh
Proof obligations (1)
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)
SW-REQ-260922-MP00
Implementing code (2)
  • bin/omarchy-menu-input
  • bin/omarchy-menu-select
Tests & evidence (1)
  • test/shell.d/menu-dmenu-test.sh
Proof obligations (2)
error_handling

Behavior when operations fail or dependencies are unavailable.

  • ✓negative (required) — test/shell.d/menu-dmenu-test.sh:112
  • ✓nominal (required) — test/shell.d/menu-dmenu-test.sh:66
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)
SW-REQ-260922-MH9B
Implementing code (1)
  • bin/omarchy-menu-images
Tests & evidence (1)
  • test/shell.d/menu-images-test.sh
Proof obligations (1)
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)
SW-REQ-260922-SWFT
Implementing code (1)
  • bin/omarchy-menu-timezone
Tests & evidence (1)
  • test/shell.d/menu-timezone-test.sh
Proof obligations (1)
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)

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