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 88ddaacOct 2, 2026, 01:32 AMpr/13968Back to current
Back to findings
Known issueKI-MENU-SELECT-SUMMON-UNBOUNDED

omarchy-menu-select blocks forever inside the omarchy-shell summon call when the IPC never returns

OpenOpenMedium

Medium-severity issue, currently open.

Description

The issue as recorded.

bin/omarchy-menu-select:91 executes omarchy-shell shell summon with no timeout wrapper. A hung IPC (summon never returns) blocks the synchronous caller indefinitely - the external-call leg of the bounded-wait obligation. Distinct from KI-MENU-SELECT-POLL-DEADLOCK, which covers the post-summon done_file poll; here the process never even reaches the poll.

Affected requirements

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

SW-REQ-260922-Q6ZS

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
Risk-rated
risk area
Availability
Security classification
Not a security surface
CVE surface
None

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
./pocs/crs-260930-k02d-c02.sh
Covers (2)
Last run Sep 30, 2026, 9:01 PM

Reproduction steps

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

./pocs/crs-260930-k02d-c02.sh

What protects you, and the fix

What limits your exposure today, and the planned remediation.

What protects you now

none - wrap caller-side invocations in an external timeout

The fix

Bound the summon: timeout <bound> omarchy-shell shell summon ... with a non-zero exit and a diagnostic on expiry

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 1 requirements · 1 code files · 1 tests.

Requirements (1)
SW-REQ-260922-Q6ZS
Code files (1)
  • omarchy-menu-select
Tests (1)
  • menu-dmenu-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

Evidence trail

The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.

  • proof/evidence/ki-menu-select-summon-unbounded.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