| Summary: | KWin Wayland fails to recover display after monitor shutoff | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | George <geowtrev> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | NEEDSINFO WAITINGFORINFO | ||
| Severity: | normal | CC: | xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.4 | ||
| Target Milestone: | --- | ||
| Platform: | EndeavourOS | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
drm info dump
monitor when unable to wake bad drm good drm kscreen-doctor -o (bad recover) kscreen-doctor -o (good state) |
||
|
Description
George
2026-01-11 22:00:40 UTC
Can you include the exact error message from the monitor? In this case, a picture would be okay. Also, please attach the output of drm_info from when the screen isn't working. You can get it from ssh. Created attachment 188457 [details]
drm info dump
Created attachment 188458 [details]
monitor when unable to wake
drm_info shows the output is set to 3840x2160@120, so the problem is on a lower level. You can report it at https://forums.developer.nvidia.com/c/gpu-graphics/linux if you're using the proprietary kernel modules, or https://github.com/NVIDIA/open-gpu-kernel-modules/issues if you're using nvidia-open (In reply to Zamundaaa from comment #4) > drm_info shows the output is set to 3840x2160@120, so the problem is on a > lower level. > You can report it at > https://forums.developer.nvidia.com/c/gpu-graphics/linux if you're using the > proprietary kernel modules, or > https://github.com/NVIDIA/open-gpu-kernel-modules/issues if you're using > nvidia-open Apologies, I uploaded the wrong drm dump. Let me get the right one quick. 😅 OK, I generated a "good" drm output and a "bad" one (generated right after a failed monitor wake). Hopefully this is useful. I can't really tell what I'm looking at.
Worth calling out too is I could access TTY without issue even with the monitor "off." That kinda caught me by surprise.
IDK if this is useful but I had Claude analyze both files and it said the main difference is this:
> Connector 135 (DP-2) shows status=1 (connected) with all 42 modes present in both states
> However, CRTC 0 mode differs:
> Working: 3840x2160@120Hz (clock: 1186810)
> Failed: 3840x2160@60Hz (clock: 533250)
Created attachment 188460 [details]
bad drm
Created attachment 188461 [details]
good drm
If you manually select the 60Hz mode, does that fail in the same way? Also, please attach the output of kscreen-doctor -o once from when the screen is ok, and once from when it's (unintentionally!) in the broken state.
You can run it from ssh with
> WAYLAND_DISPLAY=wayland-0 kscreen-doctor -o
Created attachment 188491 [details]
kscreen-doctor -o (bad recover)
Created attachment 188492 [details]
kscreen-doctor -o (good state)
(In reply to Zamundaaa from comment #10) > Also, please attach the output of kscreen-doctor -o once from when the > screen is ok, and once from when it's (unintentionally!) in the broken state. > You can run it from ssh with > > WAYLAND_DISPLAY=wayland-0 kscreen-doctor -o Attached those outputs. I did this with 60hz configured. I didn't run this with SSH. I accessed TTY (which again for some reason works even during failed resume) to run the commands. LMK if it would be better to run via SSH! Okay, so I take it manually setting the display to 60Hz does also cause the problem?
But I need the output from when it wrongly gets set to 60Hz, not from when you configure it to 60Hz. I want to find out on what level the wrong mode gets chosen.
About the output though, when you ran the command from the tty, it crashed. It looks like your distro might be patching Qt to default to xcb or something? Try with
> QT_QPA_PLATFORM=wayland WAYLAND_DISPLAY=wayland-0 kscreen-doctor -o
instead, that should hopefully make it work.
Getting it from the tty is fine for this one, only with drm_info using ssh is important, as the tty will change the drm state.
(In reply to Zamundaaa from comment #14) > Okay, so I take it manually setting the display to 60Hz does also cause the > problem? Yep (In reply to Zamundaaa from comment #14) > But I need the output from when it wrongly gets set to 60Hz, not from when > you configure it to 60Hz. I want to find out on what level the wrong mode > gets chosen. Ah good point, I will try that next. (In reply to Zamundaaa from comment #14) > About the output though, when you ran the command from the tty, it crashed. > It looks like your distro might be patching Qt to default to xcb or > something? Try with > > QT_QPA_PLATFORM=wayland WAYLAND_DISPLAY=wayland-0 kscreen-doctor -o > instead, that should hopefully make it work. > Getting it from the tty is fine for this one, only with drm_info using ssh > is important, as the tty will change the drm state. OK, I will try both of these, if I'm understanding right: - Using SSH: drm_info - From TTY: QT_QPA_PLATFORM=wayland WAYLAND_DISPLAY=wayland-0 kscreen-doctor -o Thank you so much for helping me through this, i know it's a slog :) Oops, misspoke before in response to:
> But I need the output from when it wrongly gets set to 60Hz, not from when
> you configure it to 60Hz. I want to find out on what level the wrong mode
> gets chosen.
I should say: This is good to know. :)
(In reply to George from comment #15) > OK, I will try both of these, if I'm understanding right: > - Using SSH: drm_info > - From TTY: QT_QPA_PLATFORM=wayland WAYLAND_DISPLAY=wayland-0 kscreen-doctor -o yeah. |