| Summary: | KDE Wayland multi-monitor bandwidth black screen | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Vojin <vgolubovic97> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | NEEDSINFO WAITINGFORINFO | ||
| Severity: | normal | CC: | dtombaugh, kdedev, tim, xaver.hugl |
| Priority: | NOR | Keywords: | multiscreen, regression |
| Version First Reported In: | 6.5.2 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
dmesg-drm debug
kwin drm debug |
||
|
Description
Vojin
2025-11-10 03:54:51 UTC
I saw this and I have a similar issue. Only mine has nothing to do with refresh rates. It is about resolutions. Multiple monitors with NVIDIA and Plasma(wayland) - when i have one monitor set to its native resolution of 3840x2160 and the other at its resolution of 1920x1080 (both at 60 Hz) i get the black screen with this "kwin_wayland[1761]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"". Once i set the highest monitor down to 1920x1080 no more black screen and KDE loads up just fine. I can also unplug my second monitor and it will work. If i have any monitor set above 1920x1080 just a blackscreen. And X11 works regardless. (In reply to Dirk Tombaugh from comment #1) > I saw this and I have a similar issue. Only mine has nothing to do with > refresh rates. It is about resolutions. Multiple monitors with NVIDIA and > Plasma(wayland) - > > when i have one monitor set to its native resolution of 3840x2160 and the > other at its resolution of 1920x1080 (both at 60 Hz) i get the black screen > with this "kwin_wayland[1761]: Invalid framebuffer status: > "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"". Once i set the highest monitor down > to 1920x1080 no more black screen and KDE loads up just fine. I can also > unplug my second monitor and it will work. > > If i have any monitor set above 1920x1080 just a blackscreen. > > And X11 works regardless. Can you send your specs? I am starting to believe it is related to nvidia drivers Do you know what version you had before upgrading or when it began happening? As far as I know, it was the same drivers before and after. I did have a little blip with the same thing a couple of weeks ago, then there was a kwin update/patch and it worked. The last update brought it down again. Operating System: openSUSE Tumbleweed 20251109 KDE Plasma Version: 6.5.2 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 Kernel Version: 6.17.7-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor Memory: 16 GiB of RAM (15.6 GiB usable) Graphics Processor: NVIDIA GeForce GT 1030 NVIDIA Graphics Driver: 580.105.08 I just realised I haven't sent specs
-`
.o+` ---------
`ooo/ OS: Arch Linux x86_64
`+oooo: Host: MS-7E51 1.0
`+oooooo: Kernel: 6.17.7-arch1-1
-+oooooo+: Uptime: 16 mins
`/:-:++oooo+: Packages: 1868 (pacman)
`/++++/+++++++: Shell: bash 5.3.3
`/++++++++++++++: Resolution: 3840x2160
`/+++ooooooooooooo/` DE: Plasma 6.5.2
./ooosssso++osssssso+` WM: kwin
.oossssso-````/ossssss+` Theme: Breeze-Dark [GTK2], Breeze [GTK3]
-osssssso. :ssssssso. Icons: breeze-dark [GTK2/3]
:osssssss/ osssso+++. Terminal: konsole
/ossssssss/ +ssssooo/- CPU: AMD Ryzen 9 7950X (32) @ 5.883GHz
`/ossssso+/:- -:/+osssso+- GPU: AMD ATI 72:00.0 Raphael
`+sso+:-` `.-/+oso: GPU: NVIDIA GeForce RTX 3090
`++:. `-/+/ Memory: 12569MiB / 63271MiB
.` `/
From a developer comment in bug 491751 > GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT is just a dumb side effect of a NVidia driver bug. The more relevant part of the logs in the initial message is this > Atomic modeset test failed! Please follow https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues to get a drm debug log of the failing modesets. Thanks! (In reply to TraceyC from comment #5) > From a developer comment in bug 491751 > > GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT is just a dumb side effect of a NVidia driver bug. > > The more relevant part of the logs in the initial message is this > > > Atomic modeset test failed! > > Please follow > https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues to > get a drm debug log of the failing modesets. Thanks! Thank you for information, once I come home tomorrow I will post the logs here 🐛🧹 ⚠️ 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! Created attachment 187536 [details]
dmesg-drm debug
Created attachment 187537 [details]
kwin drm debug
I added two debug files following the guide/link provided. Unfortunately that log doesn't show any issues. If that's from when the screens don't turn on, then the problem is entirely on the driver side.
I see the original report has a bunch of
> Atomic modeset test failed! Invalid argument
in the log though, which should show up in the debug log as well.
Yeah that should be from the time it was blank. I set my resolution to something I knew would cause it. The screens went blank, I then went into a console (ctrl-alt-F1) logged in and ran the script(s). The weird thing is the screen did kind of flash when I ran the scripts. I did see a cursor, but it wasn't the one I have currently set. Then it went back to blank. (In reply to Zamundaaa from comment #11) > Unfortunately that log doesn't show any issues. If that's from when the > screens don't turn on, then the problem is entirely on the driver side. > > I see the original report has a bunch of > > Atomic modeset test failed! Invalid argument > in the log though, which should show up in the debug log as well. The "Atomic Modeset test failed" is not from my stuff. I've never had that error, at least not that I could see. I'm not sure this is a driver issue. I went into Gnome and everything worked just fine. Gnome is using Wayland, and unless there is some other thing they do on top of the driver and Wayland, the driver did what it was supposed to. My screens had the proper resolutions and had no issues switching and changing resolutions and refresh rates. |