SUMMARY When trying to enable HDR for my projector screen the system freezes for 1-2 minutes before resetting the configuration to the default again. Inspecting journalctl there are hundreds of lines of ``` kwin_wayland[4108]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" ``` with an occasional `kwin_wayland_drm: Checking test buffer failed!` in-between. I can reproduce this behaviour to 100%. STEPS TO REPRODUCE 0. Open Display Configuration 1. check "Enable HDR" for the projector display 2. Click Apply OBSERVED RESULT system freezes for 1-2 minutes before reverting the configuration. EXPECTED RESULT HDR is enabled. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Kernel Version: 6.14.3-arch1-1 (64-bit) Graphics Platform: Wayland Graphics Processor: NVIDIA GeForce RTX 4070 Ti SUPER ADDITIONAL INFORMATION nvidia driver version: 570.144 I've had this issue since I first tried to enable HDR last year in July, so it's not related to a new driver update or software update. HDR worked before when running Windows. I have a 2 monitor, 1 projector, 1 receiver setup: projector: BENQ TK850 connected via HDMI to receiver: Denon AVR-X1700H which is connected via HDMI to my desktop PC. My two other monitors are connected via display port to my PC. The display name shown in the display configuration for the screen representing my projector shows the receiver name. When I turn off my projector the display is still shown as active, although resolution changes from 4k to 1920x1080 and the displays are not attached correctly anymore. Note that I need to leave the display as active, otherwise I don't get sound via my receiver. Not sure if this is helpful information. The behaviour is very similar to what the last post of https://bugs.kde.org/show_bug.cgi?id=486460 described, although I did not set any specific options (e.g. wideColorGamut).
The framebuffer warnings are a driver issue, which becomes more visible when setting the configuration doesn't work. Please follow https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues to get a drm debug log of the issue. Hopefully it'll reveal the actual underlying problem.
I started logging and enabled HDR shortly afterwards (perhaps 1-2 seconds) and stopped logging immediately once I regained control of the application. Log file is too large to upload here, let me know if this link doesn't work: https://fractalvision.spdns.org:35365/s/9ws6ErQSMnBqfCG I also added a short log file of what the log usually looks like. Not sure if it is necessary, but maybe it helps: https://fractalvision.spdns.org:35365/s/D2XTANnPs4QQ9EL
Whelp, that's unfortunately entirely useless: > [drm:drm_atomic_check_only] atomic driver check for 000000000180eae3 failed: -22 That just means "the driver says no". Best I can do here is to recommend you to take this up with NVidia, at https://forums.developer.nvidia.com/c/gpu-graphics/linux if you use the proprietary driver, or at https://github.com/NVIDIA/open-gpu-kernel-modules if you use nvidia-open
Aw, that's what I feared. Well, will do, thank you!