Bug 507285 - [Kwin] [Scene-OpenGL] [Wayland] When connecting 4 monitors to a system, system will stall on a blank screen after SDDM login
Summary: [Kwin] [Scene-OpenGL] [Wayland] When connecting 4 monitors to a system, syste...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: scene-opengl (other bugs)
Version First Reported In: 6.4.2
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-20 22:00 UTC by teelarr
Modified: 2025-11-10 17:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
This is what you should see (252.16 KB, image/png)
2025-08-27 17:33 UTC, Nate Graham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description teelarr 2025-07-20 22:00:58 UTC
SUMMARY

Upon connecting a 4th monitor to the system, logging in through SDDM on a Wayland session results in a black screen/stall, spamming journal with error messages, this is irrecoverable and the only workaround is to disconnect 1 monitor.

A snippet of the logspam is as follows: 

Jul 20 17:27:16 localhost.localdomain kwin_wayland[2227]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Jul 20 17:27:16 localhost.localdomain kwin_wayland[2227]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Jul 20 17:27:16 localhost.localdomain kwin_wayland[2227]: kwin_wayland_drm: Checking test buffer failed!
Jul 20 17:27:16 localhost.localdomain kwin_wayland[2227]: kwin_wayland_drm: Atomic modeset test failed! Invalid argument

STEPS TO REPRODUCE
1. Obtain a GPU with at least 4 ports
2. Connect 4 monitors to the GPU
3. Boot the system into SDDM 
4. Login

OBSERVED RESULT
System will hang on a black screen, rendering it unusable until a hard restart (either through REISUB or power-cycling)

EXPECTED RESULT
The system boots into the desktop with output on at least one monitor.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20250714
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor
Memory: 64 GiB of RAM (62.4 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4090

ADDITIONAL INFORMATION

This has been happening to me since at least Plasma 6.3 (I didn't test any earlier versions). 

No-repro on X11
No-repro on alternative DEs
HDR/VRR status appears to not affect this issue
Deleting kwinoutputconfig.json SOMETIMES appears to resolve this issue, but the easier solution is to physically disconnect a monitor. 

The displays in question:

1 x Dell U2715H, connected via DP
1 x Alienware U3225QF, connected via DP
1 x Dell S2721DGF, connected via DP -> HDMI adapter
1 x Onkyo NR7100 AV Reciever, connected via known-good compliant HDMI 2.1 fiber-optic cable. 

It doesn't matter which monitor is disconnected to resolve the issue, it appears no-repro on 3 monitor setups.
Comment 1 teelarr 2025-07-28 22:22:48 UTC
Just a note to say that this looks very similar to https://bugs.kde.org/show_bug.cgi?id=500819 but I am on a much higher version of Plasma, so I’m not sure if it’s related. 

This is 100% repro for me, issue does not happen if I unplug a fourth monitor.
Comment 2 Zamundaaa 2025-08-11 13:12:52 UTC
There's a good chance this is just caused by the driver not handling bandwidth limits properly. In Plasma 6.4, you can limit the color resolution to a lower value, please test if setting that on all screens helps.
Comment 3 teelarr 2025-08-12 02:54:38 UTC
I don’t see an option to set this anywhere - should it be in display options?
Comment 4 Bug Janitor Service 2025-08-27 03:47:35 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 teelarr 2025-08-27 05:23:11 UTC
Unfortunately I do not see the color resolution option in the display settings panel. Adding this info in case this is another bug in itself.
Comment 6 Nate Graham 2025-08-27 17:33:30 UTC
Created attachment 184505 [details]
This is what you should see
Comment 7 teelarr 2025-08-28 16:50:45 UTC
This option is not there for me, on a discussion thread I opened it was mentioned that it might not be supported on my RTX4090, this is the link that was given: https://drmdb.emersion.fr/properties/3233857728/max%20bpc
Comment 8 Nate Graham 2025-08-28 16:51:50 UTC
It sounds like there may be multiple hardware or driver bugs here, unfortunately. I'll let the KWin folks decide if there's anything we can do about it in KWin.
Comment 9 teelarr 2025-08-28 16:53:24 UTC
(In reply to Nate Graham from comment #8)
> It sounds like there may be multiple hardware or driver bugs here,
> unfortunately. I'll let the KWin folks decide if there's anything we can do
> about it in KWin.

Thank you! Please don’t hesitate if there’s anything more I can provide to help.
Comment 10 Zamundaaa 2025-08-29 15:35:59 UTC
Yeah, I think this needs to be reported at https://forums.developer.nvidia.com/c/gpu-graphics/linux - at a minimum, NVidia needs to add the "max bpc" property, so that we can limit bit depth, but drivers are supposed to do that automatically as well
Comment 11 teelarr 2025-10-08 00:44:44 UTC
Sorry for the additional bump - Is there anywhere else I can report this? I'm reporting as a home user, and therefore can't sign up for an NVIDIA Developer account.
Comment 12 teelarr 2025-10-08 05:09:30 UTC
I also see that 580.76.05 came with the following patch notes: 

"Added an "OutputBitsPerComponent" MetaMode attribute that can be used to control the number of bits per color component transmitted via a display connector. If not specified, the driver will choose an optimal color format."

https://www.nvidia.com/en-us/drivers/details/252613/

Is this related?
Comment 13 teelarr 2025-11-10 17:55:52 UTC
Appears to be resolved as of 580.105.08.
Comment 14 teelarr 2025-11-10 17:59:43 UTC
(With the caveat that enabling all 4 monitors results in a black screen but can eventually be cancelled with the output: 

"Couldn’t apply display configuration: The driver rejected the output configuration"

It is not longer a fatal stall that requires a forced reboot of the machine.