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.
Keybindings menu build has no deadline on hyprctl binds or xkbcli compile-keymap; a stalled callee blocks the menu
Low-severity issue, currently open.
Description
The issue as recorded.
bin/omarchy-menu-keybindings builds the keybindings menu from two external calls without a deadline. The first is hyprctl binds, which the script reads for the cache key and again in dynamic_bindings. The second is xkbcli compile-keymap </dev/null, the keymap_cmd that parse_keycodes reads through gawk getline. A stalled Hyprland IPC or a wedged keymap compile blocks the menu build for as long as the callee blocks. The keybindings menu then never opens, and the script never exits.
On the stalled-hyprctl path the script calls hyprctl binds three times in sequence: cache key, cache refresh, and the uncached fallback after the refresh fails. A per-call bound therefore costs about three times its value. pocs/9dms-keybindings-no-timeout.sh reproduces both arms on the real script in --print mode. With hyprctl stalled, the build is still blocked at a 10s watchdog (rc=124). With xkbcli stalled, the build is still blocked at a 5s watchdog (rc=124). The control arm builds the stubbed bind row in about a second, with its keycode resolved through the stubbed keymap.
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-menu-keybindings (keybindings menu build: hyprctl binds, xkbcli compile-keymap)
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/9dms-keybindings-no-timeout.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/9dms-keybindings-no-timeout.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
The defect affects only the keybindings menu. The blocked build changes and dispatches no binding. To recover, close the menu launcher, or kill the stuck hyprctl or xkbcli process. When the compositor IPC answers again, the next open works. A cached record set then loads without a call to xkbcli.
The fix
Wrap both external calls in bin/omarchy-menu-keybindings with a timeout. For example, use `timeout 2 hyprctl binds` at both call sites and `keymap_cmd = "timeout 2 xkbcli compile-keymap </dev/null"`. The existing fallback keycode table already covers a missing keymap. Consider one `hyprctl binds` read per run, so that a stall costs one timeout and not three. Then remove the SW-REQ-260922-9DMS external_call_timeout_bounded deferral and add a witness for the bounded paths. Close criterion: both stall arms of pocs/9dms-keybindings-no-timeout.sh finish inside their watchdogs, and the tripwire flips red.
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-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.