MarlonAzevedo added an October 16 report to omacom/omarchy#9156 describing an AMD laptop whose shell crashed after a monitor and USB hub were connected while locked. The recovered lock reported secure status but remained black, requiring a hard reset.
omarchybot then reported reproducing a protocol-error crash on newer packages by creating and immediately removing a headless output while locked. Its trace implicated a lock-surface request racing output removal. The bot attributed that crash to Hyprland, while explicitly leaving the subsequent black-screen behavior unexplained.
The issue remains open. The bot reported no contained Omarchy fix from that investigation and left avoiding display power-off or retaining a headless output as design choices for a maintainer.
