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.
Internal display toggle not re-applied after suspend/resume
Reported by rutger1140 · filed Apr 29, 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
System details
FW13 - AMD 7840 - Omarchy 3.6.0
What's wrong?
Summary
omarchy-hyprland-monitor-watch listens only for monitorremoved events and recovers internal display when externals disappear. There's no equivalent handler for resume-from-suspend that re-applies the internal-monitor-disable toggle, so eDP-1 comes back online on wake even when:
- Lid is closed
- External monitors are still connected
- The toggle file still exists in ~/.local/state/omarchy/toggles/
Root cause hypothesis
The toggle is implemented as a sourced Hyprland config snippet, but Hyprland's post-resume monitor reconfiguration doesn't re-source it. The watcher script catches monitorremoved but not the implicit "monitor reconfiguration on resume" scenario.
Suggested fix directions
- Extend
omarchy-hyprland-monitor-watchto also handlemonitoraddedevents with toggle-respecting logic - Add a systemd-sleep hook (
/etc/systemd/system-sleep/) that re-applies the toggle on resume - Have the post-resume path check lid state via
/proc/acpi/button/lid/*/state
Happy to submit a PR if there's a preferred direction.
View raw text
### System details FW13 - AMD 7840 - Omarchy 3.6.0 ### What's wrong? ## Summary `omarchy-hyprland-monitor-watch` listens only for `monitorremoved` events and recovers internal display when externals disappear. There's no equivalent handler for resume-from-suspend that re-applies the `internal-monitor-disable` toggle, so eDP-1 comes back online on wake even when: - Lid is closed - External monitors are still connected - The toggle file still exists in `~/.local/state/omarchy/toggles/` ## Root cause hypothesis The toggle is implemented as a sourced Hyprland config snippet, but Hyprland's post-resume monitor reconfiguration doesn't re-source it. The watcher script catches `monitorremoved` but not the implicit "monitor reconfiguration on resume" scenario. ## Suggested fix directions 1. Extend `omarchy-hyprland-monitor-watch` to also handle `monitoradded` events with toggle-respecting logic 2. Add a systemd-sleep hook (`/etc/systemd/system-sleep/`) that re-applies the toggle on resume 3. Have the post-resume path check lid state via `/proc/acpi/button/lid/*/state` Happy to submit a PR if there's a preferred direction.
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 02:51 UTC