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.
menu keybidnings broken
Reported by felixzsh · filed Jul 20, 2026Closed upstream on 2026-07-21 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
thinkpad x1 carbon 7th
What's wrong?
this are the only keybindings that i see:
<img width="2472" height="1350" alt="Image" src="https://github.com/user-attachments/assets/761a26d5-dbf4-4211-a5d0-3b5dba093743" />
after research it seems the problem is with hyprland hyprctl -j binds produces bad json, im to about to send a pr upstream trying to fix this
View raw text
### System details thinkpad x1 carbon 7th ### What's wrong? this are the only keybindings that i see: <img width="2472" height="1350" alt="Image" src="https://github.com/user-attachments/assets/761a26d5-dbf4-4211-a5d0-3b5dba093743" /> after research it seems the problem is with hyprland hyprctl -j binds produces bad json, im to about to send a pr upstream trying to fix this
- 761a26d5-dbf4-4211-a5d0-3b5dba093743
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
- Fixed bypr/6664· confirmed
- Fixed bypr/10614· confirmed
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.