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 laptop display does not automatically re-enable after external monitor is disconnected
Reported by bokology · filed Sep 20, 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
Dell Vostro 16 5630; Intel Raptor Lake-P / Iris Xe integrated graphics; Omarchy 4.0.4-1; kernel 7.2.5-3-omarchy; Hyprland 0.56.2; BIOS 1.30.0.
What's wrong?
When an external monitor is connected, turning off the laptop's internal display works. However, after the external monitor is disconnected, the internal laptop display does not automatically toggle back on. The laptop panel remains disabled/blank until it is manually re-enabled.
Expected behavior: when the external monitor is removed, Omarchy should automatically re-enable the laptop's internal display.
Steps to reproduce:
1. Start a session on the Dell Vostro 16 5630 with the internal display enabled.
2. Connect an external monitor.
3. Use Omarchy's display/monitor controls to turn off the laptop's internal display, leaving the external monitor active.
4. Disconnect/remove the external monitor.
5. Observe that the laptop's internal display does not automatically turn back on.
The current monitor configuration uses Omarchy's default modeless monitor configuration (~/.config/hypr/monitors.lua). The installed monitor watcher includes recovery logic for a disabled internal monitor when no external display is connected, but the internal display was not restored in this external-monitor-removal case.
At the time of filing, no external display is connected, so hyprctl monitors all reports only the internal eDP-1 panel (1920x1200@60). Kernel logs show the Intel i915 graphics driver initialized normally; no i915/DRM error was observed in the current boot logs.
View raw text
### System details Dell Vostro 16 5630; Intel Raptor Lake-P / Iris Xe integrated graphics; Omarchy 4.0.4-1; kernel 7.2.5-3-omarchy; Hyprland 0.56.2; BIOS 1.30.0. ### What's wrong? When an external monitor is connected, turning off the laptop's internal display works. However, after the external monitor is disconnected, the internal laptop display does not automatically toggle back on. The laptop panel remains disabled/blank until it is manually re-enabled. Expected behavior: when the external monitor is removed, Omarchy should automatically re-enable the laptop's internal display. Steps to reproduce: 1. Start a session on the Dell Vostro 16 5630 with the internal display enabled. 2. Connect an external monitor. 3. Use Omarchy's display/monitor controls to turn off the laptop's internal display, leaving the external monitor active. 4. Disconnect/remove the external monitor. 5. Observe that the laptop's internal display does not automatically turn back on. The current monitor configuration uses Omarchy's default modeless monitor configuration (`~/.config/hypr/monitors.lua`). The installed monitor watcher includes recovery logic for a disabled internal monitor when no external display is connected, but the internal display was not restored in this external-monitor-removal case. At the time of filing, no external display is connected, so `hyprctl monitors all` reports only the internal `eDP-1` panel (1920x1200@60). Kernel logs show the Intel i915 graphics driver initialized normally; no i915/DRM error was observed in the current boot logs.
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/7146· 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.
- Out of scopeDecided by agents · verified · 2026-10-09 16:31 UTC