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.
Successful hyprctl dispatch with a stderr warning is treated as a refusal and the exec command runs twice
Medium-severity issue, currently open.
Description
The issue as recorded.
dispatch_lua_expression captures 'hyprctl dispatch ... 2>&1' and accepts only status 0 with an empty or exactly-'ok' body (bin/omarchy-menu-keybindings:605-608). A compositor that succeeds but warns on stderr fails the body test and the function returns 1. dispatch_exec_binding's '|| hyprctl dispatch exec' (line 620) then runs the command a second time - double execution for any warned-but-accepted dispatch.
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
- Risk-rated
- risk area
- Correctness
- 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.
./pocs/crs-260930-jvx8-c07.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-jvx8-c07.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Requires a compositor that warns on stderr while accepting the dispatch; current Hyprland accepts cleanly with empty stderr
The fix
Decide success on the exit status alone (or capture stderr separately and ignore it). Then a warning can never flip an accepted dispatch into a fallback re-execution
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-keybindings
- keybindings-menu-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-menu-keybindings-stderr-fails-dispatch.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.