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-internal-toggle leaves laptop display black after external monitor disconnect
Reported by abbood · filed Apr 18, 2026Closed upstream on 2026-04-19 by dhh, as a duplicate of #5346 (R-4287). GitHub close reason: completed.
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
Intel Ultra 7, Intel integrated GPU, Omarchy 3.5.1, Hyprland 0.54.3, Huawei MateBook Pro VGHH-XX
What's wrong?
The new Trigger > Toggle > Laptop Display feature in 3.5.1 uses hyprctl keyword monitor "eDP-1,disable" to turn off the internal display. This works fine while the external monitor stays connected, but when the external is later disconnected (cable yanked, dock unplugged), the internal display does not automatically re-enable. The user is left with a black screen and no way to recover without either blind-typing a hyprctl command or rebooting.
Steps to reproduce:
- Connect an external display (HDMI or DisplayPort).
- Open Super + Alt + Space > Trigger > Toggle > Laptop Display to turn the internal display off. External display is now the only active display — working as intended.
- Physically disconnect the external display.
Expected: eDP-1 re-enables automatically so the user still has a usable screen.
Actual: eDP-1 stays disabled. Both displays are now effectively off. Recovering requires running hyprctl keyword monitor "eDP-1,preferred,auto,auto" blindly, or rebooting.
Root cause (speculation):
hyprctl keyword monitor ...,disable removes the monitor from Hyprland's state entirely, rather than just blanking it. On hardware where the external display's disappearance doesn't trigger Hyprland to re-scan and re-enable disabled connectors, the internal display stays gone. A DPMS-based approach (hyprctl dispatch dpms off eDP-1) keeps the monitor registered with Hyprland and recovers cleanly on external disconnect, at the cost of needing manual workspace migration before the blank.
Happy to test a fix or PR something if it'd help.
Workaround
I use a three-part setup that handles both manual toggling and automatic recovery on hotplug: (1) a manual toggle script bound to F1, (2) a user systemd service that listens to Hyprland's event socket for monitoradded/monitorremoved events (with DRM polling as a fallback), and (3) the systemd unit file. The key difference from the current Omarchy implementation is that the toggle script uses hyprctl dispatch dpms off eDP-1 instead of monitor,disable, which keeps the internal monitor registered with Hyprland. Workspaces on eDP-1 are migrated to the external monitor before blanking. On external disconnect, eDP-1 is still in Hyprland's state and DPMS-wakes cleanly.
full setup
- hyprmon-monitor-daemon
- hyprmon-daemon.service
- hyprmon-auto-switch
View raw text
### System details Intel Ultra 7, Intel integrated GPU, Omarchy 3.5.1, Hyprland 0.54.3, Huawei MateBook Pro VGHH-XX ### What's wrong? The new Trigger > Toggle > Laptop Display feature in 3.5.1 uses hyprctl keyword monitor "eDP-1,disable" to turn off the internal display. This works fine while the external monitor stays connected, but when the external is later disconnected (cable yanked, dock unplugged), the internal display does not automatically re-enable. The user is left with a black screen and no way to recover without either blind-typing a hyprctl command or rebooting. ## Steps to reproduce: 1. Connect an external display (HDMI or DisplayPort). 2. Open Super + Alt + Space > Trigger > Toggle > Laptop Display to turn the internal display off. External display is now the only active display — working as intended. 3. Physically disconnect the external display. **Expected:** eDP-1 re-enables automatically so the user still has a usable screen. **Actual:** eDP-1 stays disabled. Both displays are now effectively off. Recovering requires running hyprctl keyword monitor "eDP-1,preferred,auto,auto" blindly, or rebooting. ## Root cause (speculation): hyprctl keyword monitor ...,disable removes the monitor from Hyprland's state entirely, rather than just blanking it. On hardware where the external display's disappearance doesn't trigger Hyprland to re-scan and re-enable disabled connectors, the internal display stays gone. A DPMS-based approach (hyprctl dispatch dpms off eDP-1) keeps the monitor registered with Hyprland and recovers cleanly on external disconnect, at the cost of needing manual workspace migration before the blank. Happy to test a fix or PR something if it'd help. ## Workaround I use a three-part setup that handles both manual toggling and automatic recovery on hotplug: (1) a manual toggle script bound to F1, (2) a user systemd service that listens to Hyprland's event socket for monitoradded/monitorremoved events (with DRM polling as a fallback), and (3) the systemd unit file. The key difference from the current Omarchy implementation is that the toggle script uses hyprctl dispatch dpms off eDP-1 instead of monitor,disable, which keeps the internal monitor registered with Hyprland. Workspaces on eDP-1 are migrated to the external monitor before blanking. On external disconnect, eDP-1 is still in Hyprland's state and DPMS-wakes cleanly. full setup - [hyprmon-monitor-daemon](https://gist.github.com/abbood/578e95cb6875cc297f1daaf7d21cc93f) - [hyprmon-daemon.service](https://gist.github.com/abbood/578e95cb6875cc297f1daaf7d21cc93f) - [hyprmon-auto-switch](https://gist.github.com/abbood/578e95cb6875cc297f1daaf7d21cc93f)
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.