KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.21.0 Qt Version: 6.10.1 Kernel Version: 6.12.64-1-MANJARO (64-bit) Graphics Platform: Wayland Graphics Processor: NVIDIA GeForce RTX 3070 Driver: linux612-nvidia-open-590.48.01-2 I've recently upgraded my display to a high-refresh one. This is the only change. Now every now and then, the screen will randomly go black without displaying no signal. There's no patter to it - it may happen after SDDM login, it may happen when waking the display up, or it may happen while I'm doing something. When this happens, I can press Ctrl-Alt-F3 to go to the console, which displays just fine, and then go back to F2 where the black screen is - now there will be a CROSS (like taskkill) but nothing happens. In very rare cases, switch to console and back will revive the display, but it never does. Since the issue is very random, I cannot provide any exact steps to reproduce it. It only happens in high refresh rate modes, i.e. 240 or 360hz. Using the same display in 60 or 120hz mode, or another machine with AMD GPU and 144hz display never has these issues. I also suspect its a Wayland issues, and X11 does not have it. There is nothing wrong with the display, as I can use it in Windows for hours and it works perfectly. I'm not sure this is the right Product/Component, please move it accordingly.
Thanks for the bug report. We need some details from your system to narrow this down. First, please paste the output of this into the report while the system is working normally: kscreen-doctor -o Then, please save the output of drm_info while the bug is present to a file and attach it to thsi report. Thanks.
(In reply to TraceyC from comment #1) > while the system is > working normally: > kscreen-doctor -o 'kscreen-doctor -o ✔ Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. Output: 1 DP-2 ea5d8098-1214-4eee-8f8d-aea3728c57de enabled connected priority 1 DisplayPort replication source:0 Modes: 1:2560x1440@60.00! 2:2560x1440@360.00* 3:2560x1440@300.00 4:2560x1440@240.00 5:2560x1440@200.00 6:2560x1440@165.00 7:2560x1440@144.00 8:2560x1440@120.00 9:2560x1440@100.00 10:1920x1080@119.88 11:1920x1080@60.00 12:1920x1080@59.94 13:1920x1080@50.00 14:1280x1024@75.03 15:1280x1024@60.02 16:1280x720@59.94 17:1280x720@50.00 18:1024x768@119.99 19:1024x768@99.97 20:1024x768@75.03 21:1024x768@70.07 22:1024x768@60.00 23:800x600@119.97 24:800x600@99.66 25:800x600@75.00 26:800x600@72.19 27:800x600@60.32 28:800x600@56.25 29:720x576@50.00 30:720x480@59.94 31:640x480@119.52 32:640x480@99.77 33:640x480@75.00 34:640x480@72.81 35:640x480@59.94 36:640x480@59.93 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: disabled Wide Color Gamut: disabled ICC profile: /home/i/.local/share/icc/27M2N8500.icm Color profile source: ICC Color power preference: prefer efficiency and performance Brightness control: supported, set to 66% and dimming to 100% DDC/CI: allowed Color resolution: unknown Allow EDR: unsupported Sharpness control: unsupported ' > Then, please save the output of drm_info while the bug is present to a file and attach it to thsi report. Attached. I also attached the xkill cursor I see when this happens. Also restarting plasma with ctrl-alt-backspace brings me back to SDDM login and the system starts working again, sans all the open lost work though. > Thanks.
Created attachment 188965 [details] drm_info after the issue
Created attachment 188966 [details] xkill curson after the bug on ctrl-alt-f2
The content of attachment 188965 [details] has been deleted for the following reason: Removing due to inclusion of personally identifying information
Thanks for the extra details. The attachment with drm_info was removed because of the inclusion of personally identifying information. Can you please attach a new copy of it with personally identifying information removed?
Created attachment 188999 [details] drm_info after the issue
Thanks!