12:29 <autisticshark> there seems to be a recent change in river or wlroots, not sure, but it causes layouts to be reset because the output is lost under certain conditions. This could be if you switch to a different TTY (Ctrl+Alt+F3 or similar) and back again, or DPMS kicks in, or you use a KVM switch to share hardware. Is it really by design that those events should cause all of your tiling layouts to reset?

12:30 <autisticshark> Orignially I raised this with the wideriver author as that's the layout manager I use and it caused it to crash (segfault) initially. Discussion from here in the ticket is relevant: https://github.com/alex-courtis/wideriver/issues/38#issuecomment-3034015044

12:57 <leon-p> autisticshark: it's a wlroots change. Layout generators can work around this by simply keeping layout variables of removed outputs and re-apply them when the output appears again

12:58 <leon-p> f by "DPMS" you mean turning off the display but keeping the logical output (using zwlr-output-power-management-v1), then that really should not lead to the output ever disappearing though

13:07 <autisticshark> leon-p: thanks.. I think that's what wideriver started to do. Yeah, I did mean that for DPMS but tbh that's the one scenario I hadn't tested and assumed it would have the same issue.

14:39 <leon-p> output power management should keep the logical output around, no matter what, otherwise it wouldn't be different from just removing the output (i.e. difference bwetween wlr-randr --off and wlopm --off)

14:40 <leon-p> I think there are some setups however where the monitor detects the signal going out, then turning off which in turn causes wlroots to no longer see the physical output and removing the logical one