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.
Lua bind scan aborts on the first throwing require; every later Lua bind silently vanishes from the menu cache
Medium-severity issue, currently open.
Description
The issue as recorded.
build_lua_bind_cache dofiles the user hyprland.lua under a single pcall (bin/omarchy-menu-keybindings:241). config/hypr/hyprland.lua:14 requires default.hypr.omarchy BEFORE hypr.bindings (line 21). Omarchy loads qconsole whose console_monitor() evaluates mon.scale > 0 against the scanner's noop mock - a table-vs-number comparison that throws and kills the whole scan. The scan then never processes hypr.bindings, so every user Lua bind (rebinds and new binds alike) goes missing from the keybindings menu. Only a DEBUG=1 stderr line records why.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Fix status
Whether this is simply open, open with a fix proposed, or already fixed upstream — and the pull request / issue that tracks it.
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
- #7564
- Reported
- 2026-08-20
- Reported by
- human:github/tobi
- Vendor response
- Fix In Progress view
- Response received
- 2026-10-04
Reviewed Sep 30, 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.
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-c01.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-jvx8-c01.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
DEBUG=1 on omarchy-menu-keybindings prints the failing require
The fix
Isolate each bind registration from unrelated config code: run the dofile with a permissive mock (never-throwing comparisons), or scan binds via a per-require pcall boundary. Then one throwing module cannot drop unrelated binds
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-scan-dofile-abort.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.