https://bugs.kde.org/show_bug.cgi?id=496631

            Bug ID: 496631
           Summary: External Monitor not waking up properly
    Classification: Plasma
           Product: Powerdevil
           Version: 6.2.3
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: plasma-b...@kde.org
          Reporter: evors...@protonmail.com
                CC: natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 176079
  --> https://bugs.kde.org/attachment.cgi?id=176079&action=edit
Journal of the run described here.

SUMMARY
My system is set to switch off its monitors after a period of inactivity, but
not suspend or hibernate. So, only monitors are switched off until I wiggle a
mouse or hit a key. 

Up until about a week ago, this hardware worked perfectly, and after a boot, it
also works perfectly, so I am sure this issue is not hardware related. 

When the monitors are turned on, the internal monitor on the laptop works
normally. The external monitor looks like it is coming out of its powersave
state, but after a second or so tells me that it has no signal and goes back to
sleep. 
At the same time, KDE extends my desktop to this monitor. After a few seconds,
KDE removes this monitor from the configuration, and displays all my windows on
the internal monitor on the laptop. Before you can do anything, KDE then
realizes there is an external monitor connected, tries to wake it up and
extends the display area to it. 

This process repeats indefinitely, rendering the computer unusable. 
If I switch off the external monitor, KDE extends my desktop to it, and stays
that way. 

If I physically unplug the monitor, KDE displays the appropriate desktop size,
and I can use the computer again. However, if I plug the monitor back in, this
little dance resumes. 

When powering off the computer completely, and connecting the monitor to it,
and then powering up, it works normally, as it used to do up until a week or so
ago. Then, if I wander away from the computer and leave it alone for long
enough for the monitors to go to sleep, it enters this state again. 

STEPS TO REPRODUCE
1. Leave computer alone for long enough for the monitors to go to sleep.
2. Wake up the computer by wiggling mouse, or pressing a key on the keyboard.

OBSERVED RESULT
External Monitor is not properly woken up, and KDE is extending the desktop to
a monitor that is not on/ready.

EXPECTED RESULT
External Monitor to be properly woken up, and given enough time to get ready.
While it is getting ready, the desktop must not be extended to it.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-arch1-1.1-g14 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7945HX3D with Radeon Graphics
Memory: 62.0 GiB of RAM
Graphics Processor: AMD Radeon 610M
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Strix G733PYV_G733PYV
System Version: 1.0

ADDITIONAL INFORMATION
It is an Optimus laptop, with an nVidia 4090 mobile GPU. Latest nvidia-open
dkms drivers are installed.


I will attach a journal of the run where I let the system run like this for a
little while. It is a little wordy, but blocks of errors like this is what is
most interesting to me:
---------------------snip-------------------
Nov 24 07:50:10 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 9748, resource id: 16777272, major code: 129 (SHAPE),
minor >
Nov 24 07:50:25 Evert.Strix google-chrome-stable[2928]:
[2923:2950:1124/075025.343187:ERROR:registration_request.cc(291)] Registration
response error messa>
Nov 24 07:52:23 Evert.Strix kwin_wayland[1245]: kf.windowsystem: static bool
KX11Extras::mapViewport() may only be used on X11
Nov 24 07:53:41 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 12492, resource id: 16777302, major code: 129 (SHAPE),
minor>
Nov 24 07:57:10 Evert.Strix google-chrome-stable[2928]:
[2923:2950:1124/075710.921921:ERROR:registration_request.cc(291)] Registration
response error messa>
Nov 24 08:06:53 Evert.Strix kwin_wayland[1245]: kf.windowsystem: static bool
KX11Extras::mapViewport() may only be used on X11
Nov 24 08:16:06 Evert.Strix kwin_wayland[1245]: kf.windowsystem: static bool
KX11Extras::mapViewport() may only be used on X11
Nov 24 08:21:02 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 14652, resource id: 16777362, major code: 129 (SHAPE),
minor>
Nov 24 08:22:12 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 14789, resource id: 16777368, major code: 129 (SHAPE),
minor>
Nov 24 08:23:07 Evert.Strix kwin_wayland[1245]: kf.windowsystem: static bool
KX11Extras::mapViewport() may only be used on X11
Nov 24 08:23:07 Evert.Strix google-chrome-stable[2928]:
[3001:3001:1124/082307.807155:ERROR:shared_image_manager.cc(250)]
SharedImageManager::ProduceSkia: >
Nov 24 08:23:48 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 15839, resource id: 16777392, major code: 129 (SHAPE),
minor>
Nov 24 08:24:04 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 15933, resource id: 16777395, major code: 129 (SHAPE),
minor>
Nov 24 08:24:52 Evert.Strix google-chrome-stable[2928]:
[2923:2923:1124/082452.773965:ERROR:interface_endpoint_client.cc(725)] Message
0 rejected by interf>
Nov 24 08:25:42 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 16143, resource id: 16777406, major code: 129 (SHAPE),
minor>
Nov 24 08:27:06 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 16468, resource id: 16777415, major code: 129 (SHAPE),
minor>
Nov 24 08:28:44 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 16727, resource id: 16777430, major code: 129 (SHAPE),
minor>
Nov 24 08:30:06 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 16969, resource id: 16777445, major code: 129 (SHAPE),
minor>
Nov 24 08:31:14 Evert.Strix google-chrome-stable[2928]:
[2923:2923:1124/083114.462826:ERROR:interface_endpoint_client.cc(725)] Message
0 rejected by interf>
Nov 24 08:33:16 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 17177, resource id: 16777451, major code: 129 (SHAPE),
minor>
Nov 24 08:35:53 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 17425, resource id: 16777463, major code: 129 (SHAPE),
minor>
Nov 24 08:36:45 Evert.Strix kwin_wayland[1245]: kwin_core: XCB error: 3
(BadWindow), sequence: 17561, resource id: 16777466, major code: 129 (SHAPE),
minor>
Nov 24 08:45:50 Evert.Strix kwin_wayland[1245]: kf.windowsystem: static bool
KX11Extras::mapViewport() may only be used on X11
Nov 24 08:58:46 Evert.Strix kded6[1408]: org.kde.pulseaudio: No object for name
"alsa_output.pci-0000_01_00.1.hdmi-stereo"
Nov 24 08:58:46 Evert.Strix plasmashell[1463]: org.kde.pulseaudio: No object
for name "alsa_output.pci-0000_01_00.1.hdmi-stereo"
Nov 24 08:58:47 Evert.Strix org_kde_powerdevil[1524]: Sleep event.
connector=card1-eDP-1, dref not set
Nov 24 08:58:49 Evert.Strix org_kde_powerdevil[1524]: Emitting
DDCA_Display_Status_Event( 8363.108:  DDCA_EVENT_DPMS_ASLEEP, card1-eDP-1,
dref: Display_Ref>
Nov 24 08:58:49 Evert.Strix org_kde_powerdevil[1524]: Executed 1 registered
callbacks.
Nov 24 09:06:01 Evert.Strix kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL
link training failed.
Nov 24 09:06:01 Evert.Strix systemd[1]: Started
dbus-:1.2-org.kde.powerdevil.backlighthelper@3.service.
░░ Subject: A start job for unit
dbus-:1.2-org.kde.powerdevil.backlighthelper@3.service has finished
successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dbus-:1.2-org.kde.powerdevil.backlighthelper@3.service
has finished successfully.
░░ 
░░ The job identifier is 3773.
------------------------------snip-------------------------

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to