OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
display-monitors critical occasional DISPUTE

Fix Hyprland hanging at startup from a rule on a disconnected port

archendeavouroscachyosomarchyhyprlandwayland
AUDITED Audited against its sources and confirmed accurate.

Symptom

Hyprland hangs completely at startup (black or frozen screen, bar never draws, mouse may still move) on a machine where you wrote a monitor rule for a port that currently has nothing plugged into it (very common on Apple Silicon/Asahi, where DP-1 is always exposed).

Cause

When the kernel exposes a connector but reports it disconnected with no EDID/modes, and you have an explicit rule for that connector, Hyprland enables the output anyway. It gets a 0x0 framebuffer, bar/layer surfaces are created on the bogus output and never commit, and the renderer stalls.

Fix

Always keep a catch-all fallback rule *after* your explicit rules, so unmatched or failed outputs degrade gracefully. In ~/.config/hypr/monitors.lua:


hl.monitor({ output = "DP-1", mode = "3840x2160@30", position = "2560x0", scale = 1 })
hl.monitor({ output = "", mode = "preferred", position = "auto", scale = 1 })   -- fallback

On Hyprland <= 0.54 (~/.config/hypr/monitors.conf):


monitor=DP-1,3840x2160@30.0,2560x0,1.0
monitor=,preferred,auto,1

If you are already frozen, get to a TTY with Ctrl+Alt+F2 and comment out the explicit rule:


sed -i 's|^hl.monitor({ output = "DP-1"|-- &|' ~/.config/hypr/monitors.lua

Verify

Boot with nothing plugged into that port: Hyprland comes up, and hyprctl monitors all shows the connector as disabled rather than 0x0-enabled.

Sources

explicit-rule-on-disconnected-connector-freezes