10:56 <Inga> Hi everybody! Is it possible that in River v3, the logic around "process keyboard input even when there are no display outputs enabled" or "keep focus on the last focused window even after all display outputs were disabled" has changed? Trying to figure out what part of my system can be responsible for the problem I'm experiencing.

11:00 <Inga> (The problem: I have a laptop and an external display which I'm also using as an USB-C dock. The power button on the external display unreasonably just powers it off, cutting off power to laptop and disabling all USB devices connected to it. To work around it, I created a script that disables the external screen with way-displays, listens for

11:00 <Inga> keyboard input, and reenables the screen after the keyboard input; this script worked fine even with the closed laptop lid. However, after I upgraded the system (which involved upgrading river from 0.2.6 to 0.3.3), it stopped reacting to keyboard input unless I open the lid. I just cannot figure out what has changed and what can be the reason and

11:00 <Inga> how to debug it, and not sure whether it's river or wlroots or something else that has changed.)

11:07 <Inga> I see many potentially related entries in river 0.3 full changelog, but I don't know enough about river implementation details to understand whether they can actually be related or not