Bug 462626 - Dual Monitor setup: Primary Display does not wake up after energy save mode
Summary: Dual Monitor setup: Primary Display does not wake up after energy save mode
Status: RESOLVED DUPLICATE of bug 460341
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.27.4
Platform: Manjaro Linux
: NOR major
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-04 10:04 UTC by Julius R.
Modified: 2023-04-17 15:30 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julius R. 2022-12-04 10:04:53 UTC
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
Comment 1 Nate Graham 2022-12-05 19:19:42 UTC
Are one or both displays connected to an NVIDIA GPU, by any chance?
Comment 2 Julius R. 2022-12-05 22:22:24 UTC
(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.
Comment 3 Julius R. 2022-12-05 22:24:21 UTC
(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.
Comment 4 Nate Graham 2022-12-06 00:33:43 UTC
Yep.

*** This bug has been marked as a duplicate of bug 460341 ***
Comment 5 joseteluisete 2023-04-16 22:24:44 UTC Comment hidden (spam)
Comment 6 joseteluisete 2023-04-17 04:49:00 UTC Comment hidden (spam)
Comment 7 Nate Graham 2023-04-17 15:30:13 UTC Comment hidden (spam)