Now that I’ve solved one bug with using the Wayland Plasma session, there’s one more big issue I need to deal with: It appears the session will crash if I use “System Settings - Hardware - Power Management - Energy Saving - Screen Energy Saving” right after the screen powers off. The monitor will first go into standby once the mouse hasn’t been moved for the given amount of minutes, but will immediately wake up afterward. When it does I can briefly see the console, followed by the login screen from which I need to log in again. This is quite problematic as I can’t power off my screen to preserve its lifetime as well as electricity consumption. I looked but haven’t seen any open bug reports on this… figured I’d ask here first before opening one to avoid duplication if the issue is known.
I have a 1080p / 144 Hz monitor connected via DisplayPort cable (no converters). I also have a cheap 1080p / 60 Hz VR headset connected over a DVI port (DVI to HDMI converter), it’s completely disabled from the system settings and should have no influence.
Sounds like it’s likely the same thing. Can’t believe there’s not one review or comment on that bug for months… Wayland is so important yet it’s like the Linux community is struggling to find anyone who will look at it. Truth be told this one sounds like it should be reported to Wayland itself… I’ll see about making a bug on the Freedesktop tracker today, maybe linking that one too. Thanks for mentioning.
Confirming it’s most likely the same issue: I enabled my VR headset as a secondary display then turned on monitor standby again. The displays switched but this time there was no actual crash.
Part of the problem is that modern monitors no longer seem to support classic standby mode, especially not over HDMI and DP connections; They completely cut off the signal until the mouse is moved again. Even back when this worked, Discord would always notify me of a new HDMI audio device whenever the monitor came back online, indicating the system lost connection when it powered off and saw it as a newly connected device when it came back on. I looked in the monitor’s settings too but am not sure if this can be fixed.
The KWin compositor should be able to handle this situation regardless of the display behaviour. FWIW, an informative discussion here about monitors, HDMI, and standby behaviours.