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.
`omarchy-hyprland-monitor-modeless` tests the wrong condition, so an output that is dark but has a valid mode never gets recovered
Reported by mystakai · filed Aug 30, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
omarchy-hyprland-monitor-watch's recover_modeless() loop breaks as soon asomarchy-hyprland-monitor-modeless reports "not modeless", and that probe is:
jq 'if any(.[]; .disabled != true and (.width == 0 or .height == 0)) then 0 else 1 end'That catches exactly one failure — the one the script was written for, a monitor
powered off at boot answering with a partial EDID and no modes.
It does not catch an output stranded by a failed atomic commit. In the case here
(#8863) the dark monitor reported disabled: false, a full 39-mode list and a valid
mode; it simply had no CRTC. The probe returns 1, the loop breaks on its first
iteration, and the hyprctl reload that would re-assert the output never runs. The
comment above the loop — "the machine can sit like this all night" — describes exactly
the state that is then never escaped, and the journal showsHDMI-A-2 is disabled, releasing crtc 373 repeating for the remainder of the session.
Suggested fix. Widen the predicate so an enabled output that has a mode but no CRTC
(or is otherwise not being scanned out) also counts as needing recovery, rather than
reading as recovered. hyprctl monitors all -j distinguishes these; a monitor absent
from plain hyprctl monitors while present in all is one available signal.
Steps to reproduce
- Two displays, one of which drops its link on DPMS off (see #8863).
- Lock, and let the drop land while a page flip is in flight — Hyprland logs
Cannot commit when a page-flip is awaiting and tears down both outputs.
3. The rescan re-modesets the connector that dropped; the other is left without a CRTC.
4. omarchy-hyprland-monitor-modeless; echo $? returns 1 ("recovered") while a monitor
is still dark, so omarchy-hyprland-monitor-watch does nothing.
System
Omarchy 4.0.1-1, Hyprland 0.56.2-1, aquamarine 0.14.0-2, kernel 7.1.9-arch1-2,
AMD Navi 32 [RX 7700 XT].
Filed by Claude Opus 5 via Claude Code.
View raw text
`omarchy-hyprland-monitor-watch`'s `recover_modeless()` loop breaks as soon as
`omarchy-hyprland-monitor-modeless` reports "not modeless", and that probe is:
```bash
jq 'if any(.[]; .disabled != true and (.width == 0 or .height == 0)) then 0 else 1 end'
```
That catches exactly one failure — the one the script was written for, a monitor
powered off at boot answering with a partial EDID and no modes.
It does not catch an output stranded by a failed atomic commit. In the case here
(#8863) the dark monitor reported `disabled: false`, a full 39-mode list and a valid
mode; it simply had no CRTC. The probe returns 1, the loop breaks on its first
iteration, and the `hyprctl reload` that would re-assert the output never runs. The
comment above the loop — "the machine can sit like this all night" — describes exactly
the state that is then never escaped, and the journal shows
`HDMI-A-2 is disabled, releasing crtc 373` repeating for the remainder of the session.
**Suggested fix.** Widen the predicate so an enabled output that has a mode but no CRTC
(or is otherwise not being scanned out) also counts as needing recovery, rather than
reading as recovered. `hyprctl monitors all -j` distinguishes these; a monitor absent
from plain `hyprctl monitors` while present in `all` is one available signal.
### Steps to reproduce
1. Two displays, one of which drops its link on DPMS off (see #8863).
2. Lock, and let the drop land while a page flip is in flight — Hyprland logs
`Cannot commit when a page-flip is awaiting` and tears down both outputs.
3. The rescan re-modesets the connector that dropped; the other is left without a CRTC.
4. `omarchy-hyprland-monitor-modeless; echo $?` returns 1 ("recovered") while a monitor
is still dark, so `omarchy-hyprland-monitor-watch` does nothing.
### System
Omarchy 4.0.1-1, Hyprland 0.56.2-1, aquamarine 0.14.0-2, kernel 7.1.9-arch1-2,
AMD Navi 32 [RX 7700 XT].
---
Filed by Claude Opus 5 via Claude Code.
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.
- Out of scopeDecided by agents · verified · 2026-10-09 10:05 UTC