| Summary: | Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Alexis NICOLAS <alexis> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REOPENED --- | ||
| Severity: | crash | CC: | contact, davidgillig9, fusionz916, irangarciaieg, jonathansimon, kontakt, kryptokatalyst, lionelg+kde, mail, ponyosunshine, thezenzombie, xaver.hugl |
| Priority: | NOR | ||
| Version: | 6.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Alexis NICOLAS
2024-06-21 23:52:06 UTC
I should have added, I have no issue login in into a Plasma X11 session. After deleting ~/.config/kwinoutputconfig.json, I could login. I did some tests and the issue happens when HDR is enabled. In the config file that put "highDynamicRange" and "wideColorGamut" to "true". Just changing "highDynamicRange" to "false" doesn't work, but if I put both to "false", I can login again. So if you enable HDR while in the session, that works, and only if you log in with HDR already enabled, it fails? I am having the same issue. I enable HDR and try to reboot I get the No Signal screen when login into a Wayland session. Also unable to switch TTYs. Changing "highDynamicRange" and "wideColorGamut" to "false" in the kwinoutputconfig.json and making the file immutable allowed me to log back into the Wayland session. (In reply to Zamundaaa from comment #3) > So if you enable HDR while in the session, that works, and only if you log > in with HDR already enabled, it fails? Yes. I can enable HDR once I login without issue and the screen does switch to HDR mode. But if I let it enabled and I reboot, I get "No Signal". I also starting having this on Arch/Nvidia 550 when KDE updated to 6.1 in the `extra` repo. Relevant `journalctl` output: Repeated: >Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible >Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Followed by single: > Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_wayland_drm: Checking test buffer failed! > Jun 20 17:03:07 gogeta kwin_wayland[2604]: kwin_core: Applying output config failed! Issue exists under every permutation of [NVIDIA DRM](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting). > OS: Arch Linux x86_64 > Host: X570S I AORUS PRO AX (-CF) > Kernel: Linux 6.9.6-arch1-1 > Uptime: 15 hours, 28 mins > Packages: 970 (pacman) > Shell: bash 5.2.26 > Display (AW3225QF): 3840x2160 @ 120Hz (HDMI 2.1) > DE: KDE Plasma 6.1.0 > WM: KWin (X11) > WM Theme: Breeze > Theme: Breeze (Dark) [QT], Breeze-Dark [GTK2], Breeze [GTK3/4] > Icons: breeze-dark [QT], breeze-dark [GTK2/3/4] > Font: Noto Sans (10pt) [QT], Noto Sans (10pt) [GTK2/3/4] > Cursor: breeze (24px) > Terminal: yakuake 24.05.1 > CPU: AMD Ryzen 5 5600 (12) @ 3.50 GHz > GPU: NVIDIA GeForce RTX 4070 SUPER [Discrete] Have just been leaving HDR off until it's resolved, and X11 for gaming until official NVIDIA driver update for explicit sync. Also, same behavior as submitter: 1. Backup .config/kwinoutputconfig.json 2. Enable HDR in Wayland session (nothing else) everything works fine during that session. 3. Reboot or re-log and I get: w/o nvidia in initramfs & nvidia_drm.modeset=1 and nvidia_drm.fbdev=1 > Black screen w/white cursor w/nvidia in initramfs & nvidia_drm.modeset=1 and nvidia_drm.fbdev=1 > No signal to display 4. Login to X11 session and restore .config/kwinoutputconfig.json 5. Reboot/re-log into Wayland session; everything fine again (HDR off) I am also experiencing the exact same problem and have found the same temporary solution to work. Same problem here, though I had to make kwinoutputconfig.json read only for Plasma to start in Wayland Same issue with nvidia 555.58 driver and the following: Operating System: Arch Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13900KS Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 Deleting '~/.config/kwinoutputconfig.json' temporarily fixes the issue. I haven't been able to reproduce this issue with driver 555.58 with a laptop rtx 3060 myself. Is it 100% reproducible for you, or does it only happen sometimes? (In reply to Zamundaaa from comment #11) > I haven't been able to reproduce this issue with driver 555.58 with a laptop > rtx 3060 myself. Is it 100% reproducible for you, or does it only happen > sometimes? Nvidia 555 hit the `extra` repo (Arch) a couple days ago and the Issue is not happening for me on this driver (555.58). It was happening 100% of the time on 550.90. I can confirm, upgrading to Nvidia 555.58 and a reboot fixed the bug for me. I can start KDE / Plasma with HDR enabled and everything starts correctly without needing to hack a conf file. Great! Probably just a weird driver bug then Hi, I can still reproduce this after just having upgraded the nvidia drivers from 555.58 to 555.58.02. I have `nvidia-drm.modeset=1` and `nvidia-drm.fbdev=1`. When I start into the Wayland session from SDDM with HDR enabled, I loose all display output and switching to a different tty no longer works. I can boot up to SDDM, switch to a different tty, disable HDR in `~/.config/kwinoutputconfig.json` and then just start the Wayland session no problem. Also enabling HDR when already in the session works. Operating System: EndeavourOS KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 AORUS MASTER (In reply to Kai from comment #15) > Hi, > > I can still reproduce this after just having upgraded the nvidia drivers > from 555.58 to 555.58.02. I have `nvidia-drm.modeset=1` and > `nvidia-drm.fbdev=1`. When I start into the Wayland session from SDDM with > HDR enabled, I loose all display output and switching to a different tty no > longer works. I can boot up to SDDM, switch to a different tty, disable HDR > in `~/.config/kwinoutputconfig.json` and then just start the Wayland session > no problem. Also enabling HDR when already in the session works. > > Operating System: EndeavourOS > KDE Plasma Version: 6.1.1 > KDE Frameworks Version: 6.3.0 > Qt Version: 6.7.2 > Kernel Version: 6.9.7-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz > Memory: 31.2 GiB of RAM > Graphics Processor: NVIDIA GeForce RTX 2080/PCIe/SSE2 > Manufacturer: Gigabyte Technology Co., Ltd. > Product Name: Z390 AORUS MASTER I just verified that I have the same Nvidia kernel flags enabled as you, Pacman says 555.58-2 installed. Nvidia tools ( nvidia-smi, nvidia-settings ) both say 555.58 ( no .2 on the end ), so I'm not sure which to tell you exactly. I am also running EndeavourOS. I am also using the same kernel as you. The only difference I could possibly think is that I had the LTS kernel installed from reading a different solution and removed it right before the system upgrade. Other than that, I have been having perfect results, surviving a reboot, and now it is also surviving turning off my hdmi tv for lengths of time and coming back without a session restart. I'm using an RTX 3060, I'm a Ryzen 5, I am on the same version of Plasma, Frameworks, and QT as you as well. Have you tried to create a new user, separate from you main, to isolate that it isn't something else in your confs that might also be triggering this? This is also happening to me on any 555.58.x driver, although my primary display is black on Wayland or X11 not just on Wayland. If I back down to 550.90.07, it's fine under X11. Wayland is iffy on that version for me. Operating System: EndeavourOS KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × 11th Gen Intel® Core™ i9-11900K @ 3.50GHz Memory: 62.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 Manufacturer: ASUS I can still reproduce the issue after upgrading the Nvidia driver to 555.58.02 (and fully up to date ArchLinux). I get the same behavior and the exact same kind of error messages: juil. 04 05:13:16 galeanthrope-mini kwin_wayland[1404]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible juil. 04 05:13:16 galeanthrope-mini kwin_wayland[1404]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" For me the issue can be reproduced 100% of the time. If I have the wrong configuration (HDR enabled), I get "No Signal" every time. When I want to go back to a good configuration, I do like Kay and switch to a TTY while I'm still at the SDDM screen. Can confirm with the lastest nvidia drivers (nvidia 555.58.02-1) in arch this problem still exists. If HDR is enabled on boot the GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT errors still occur under wayland session. *** Bug 488670 has been marked as a duplicate of this bug. *** |