I am using 2 Displays: One is connected as primary on DP4, the other one is a secondary display in another room, connected via HDMI1. When the displays are powered off due to energy saving schedule, the primary display does not wake up again. When triggering the wake up (mouse movement, key input), the displays both get powered up again (as can be seen by the stanby LEDs), but the primary stays black. In the .local/share/kscreen config file, the line with "enabled" seems to be stuck at "false". Once I manually unplug the second display (HDMI1), the primary display shows the desktop again. Complete Bug description with steps taken to alleviate: https://forum.manjaro.org/t/monitor-does-not-turn-back-on-after-energy-saving/128030/4
Are one or both displays connected to an NVIDIA GPU, by any chance?
(In reply to Nate Graham from comment #1) > Are one or both displays connected to an NVIDIA GPU, by any chance? Hi Nate, both are connected to one Nvidia RTX 3070 indeed.
(In reply to Nate Graham from comment #1) > Are one or both displays connected to an NVIDIA GPU, by any chance? You are right, it is probably 460341.
Yep. *** This bug has been marked as a duplicate of bug 460341 ***
Hi! I don't know if this is the right place to write this. When my system wakes up I just see the mouse and a black screen. I can change between apps with Alt+Tab and I can open apps assigned to keys, Meta+E > Dolphin, for example. I don't see the task manager or the Desktop. I opened a topic in Manjaro Forums. As I mention there I have realized this happens after installing some particular packages. https://forum.manjaro.org/t/screen-stays-off-after-waking-up/138830 The fact is I have a Monitor and a TV but I don't use Nvidia. I just use the Intel GPU inside the i9 processor. I use HDMI and DVI cables. I don't know if that's important to mention.
In my previous post, I failed to specify the correct Plasma version. It's 5.27.4. I have also seen that I don't know exactly when this problem started. I thought it did when installing some particular packages but I was wrong. I guess I had no problems with version 5.26.5.
Hi Jose, Please submit a new bug report for that issue. Thanks!