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-hyprland-session-locked has no deadline on hyprctl -j monitors; a stalled compositor IPC hangs the probe
Low-severity issue, currently open.
Description
The issue as recorded.
bin/omarchy-hyprland-session-locked asks the compositor for the lock state with monitors=$(hyprctl -j monitors 2>/dev/null) || exit 2. Nothing puts a deadline on that call. Sometimes the Hyprland IPC socket accepts the request but never answers. This happens in practice around lid and monitor transitions. The probe then blocks for as long as hyprctl blocks, instead of returning exit 2 (undetermined).
The stranded-lock recovery path calls this probe. That path then waits on a probe that never reports, so recovery makes no progress for the duration of the stall. The Hyprland failsafe lock screen is the backstop, so the session stays locked. pocs/eh0k-hyprctl-monitors-no-timeout.sh reproduces the defect. With hyprctl stalled, an external 5s watchdog kills the real probe (rc=124). The control arms answer 0 (locked) and 1 (unlocked) immediately.
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
- risk area
- Availability
- CVE surface
- None
Where it is
The code the issue lives in — peek the affected function inline to see it in context.
- bin/omarchy-hyprland-session-locked (lock-state probe used by stranded-lock recovery)
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.
./pocs/eh0k-hyprctl-monitors-no-timeout.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/eh0k-hyprctl-monitors-no-timeout.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
This defect never unlocks the session. A stalled probe only delays stranded-lock recovery, and the Hyprland failsafe lock screen stays in place. When the compositor IPC answers again, the next probe returns a real verdict. To recover by hand, kill the stuck hyprctl process, or switch to a TTY and restart the lock.
The fix
Bound the IPC call in bin/omarchy-hyprland-session-locked, for example `monitors=$(timeout 2 hyprctl -j monitors 2>/dev/null) || exit 2`. A stalled compositor then maps to the existing exit 2 (undetermined), which callers already handle. Then remove the SW-REQ-260912-EH0K external_call_timeout_bounded deferral and add a witness for the bounded path. Close criterion: pocs/eh0k-hyprctl-monitors-no-timeout.sh flips red, because the stall arm returns exit 2 inside the watchdog.
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-hyprland-session-locked
- hyprland-session-locked-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.
- proof/evidence/ki-lock-probe-hyprctl-no-timeout.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.