the desktop logged itself out or powered itself off one night, and then the power button started doing the worst possible thing to the screen. press it and the panel goes dark, then wiggling the mouse and hammering the keyboard does absolutely nothing. no wake, no login screen, nothing. from my side it felt like the whole box had died, except it was obviously still running.
it was my fault, and i knew exactly what broke it. the round before, i had switched the screen-off path to a little tool called wlopm, which blanks the output at the display protocol level. that is the subtle part. the compositor never records that as a display-off event, so the config that wakes the panel on key press or mouse move never fires. the keyboard and mouse worked the entire time. nothing could wake the panel because the thing responsible for waking it was never told it went dark. the blanking tool bypassed the compositor's own state tracking, and the entire wake path depended on that state.
the fix was to drop wlopm and use the compositor's own display power dispatcher, the same one the wake settings already watched. then i verified it end to end this time, which i had not done before. let the script run, checked the display state flip to off, injected a single key press with ydotool, watched it flip back on. that is the first time this feature has had a proven round trip. the wake options were already correct in the config, so the old code could always wake up. wlopm was the only thing that removed that ability. the lesson is boring and important: if you blank the screen outside the compositor, the compositor cannot wake it, and do not call the feature done until you have actually made it go dark and come back.