Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Submap 'catchall' triggers global binds when defined first
Reported by coder0x6675 · filed Jan 22, 2026Closed upstream on 2026-01-23 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Arch Linux / 6.18.5-zen1-1-zen
What's wrong?
Edit: Accidentally posted in the wrong repo. My bad.
Environment
- Distro/Kernel: Arch Linux / 6.18.5-zen1-1-zen
- Hyprland: 0.53.1 (commit
ab1d80f) - GPU: amdgpu
Steps to Reproduce
Place the submap definition above a conflicting global bind:
bind = SUPER, R, submap, LAUNCH
submap = LAUNCH
bindi = , I, exec, notify-send "Submap action"
bindi = , catchall, submap, reset
submap = reset
bind = SUPER, I, exec, notify-send "Global action"
- Enter submap (
SUPER+R). - Press
SUPER+I.
Issue
Both binds execute. "Global action" fires first, followed by "Submap action". This suggests the submap exit propagates the event to the global scope if the global bind is parsed later in the config.
Solution/Workaround
Defining the global bind before the submap block prevents the double execution:
bind = SUPER, I, exec, notify-send "Global action"
bind = SUPER, R, submap, LAUNCH
# ... submap definition ...
Edit: Accidentally posted in the wrong repo. My bad.
View raw text
### System details Arch Linux / 6.18.5-zen1-1-zen ### What's wrong? Edit: Accidentally posted in the wrong repo. My bad. ## Environment * **Distro/Kernel:** Arch Linux / 6.18.5-zen1-1-zen * **Hyprland:** 0.53.1 (commit `ab1d80f`) * **GPU:** amdgpu ## Steps to Reproduce Place the submap definition **above** a conflicting global bind: ```ini bind = SUPER, R, submap, LAUNCH submap = LAUNCH bindi = , I, exec, notify-send "Submap action" bindi = , catchall, submap, reset submap = reset bind = SUPER, I, exec, notify-send "Global action" ``` 1. Enter submap (`SUPER+R`). 2. Press `SUPER+I`. ## Issue **Both** binds execute. "Global action" fires first, followed by "Submap action". This suggests the submap exit propagates the event to the global scope if the global bind is parsed later in the config. ## Solution/Workaround Defining the global bind **before** the submap block prevents the double execution: ```ini bind = SUPER, I, exec, notify-send "Global action" bind = SUPER, R, submap, LAUNCH # ... submap definition ... ``` --- **Edit:** Accidentally posted in the wrong repo. My bad.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.