Bug 470383

Summary: Displays connected through USB-C Dock give black display until 24-bit color mode is forced
Product: [Plasma] kwin Reporter: Shawn W Dunn <sfalken>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.27.5   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Shawn W Dunn 2023-05-29 01:32:50 UTC 
Using a Lenovo Thinkpad T16 AMD, and Lenovo Universal USB-C Dock, a plasma-wayland session gives me no output to the displays.  kscreen *sees* the displays there, but the displays remain blank.   This behavior is the same whether I have the dock and displays plugged in while booting, or if I plug the dock into an already booted plasma-wayland session.

STEPS TO REPRODUCE
1. Plug displays via displayport cables into USB-C Dock 
2. Plug Dock into Laptop


OBSERVED RESULT
No Output to dock connected displays, but all other dock functions work (audio passthrough, mouse/keyboard, etc), Kscreen reports the displays are there and enabled, but displays remain blank.

EXPECTED RESULT
Output of Graphical desktop to dock attached displays

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.5.19

ADDITIONAL INFORMATION

This behavior is the same for me on both openSUSE Tumbleweed, and Fedora 38, so it doesn't appear to be a distro specific issue.   Not that it matters to wayland, but using plasma-x11 also is problematic.   The Dock works *fine* and as expected in Gnome 44, for both X11 and Wayland sessions, on both openSUSE and Fedora
Comment 1 Shawn W Dunn 2023-05-29 19:39:48 UTC 
Setting KWIN_DRM_PREFER_COLOR_DEPTH=24 in `/etc/profile` fixes this issue.

Per suggestion from the user that helped me in the Plasma matrix channel, I have filed a bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2598
Comment 2 Nate Graham 2023-05-31 13:54:27 UTC 
Sounds like a driver bug. Not sure how we could fix this ourselves in KWin. Would it be possible to detect that there's no output and try to switch to 24-bit mode? If not, we probably have to wait for the driver bug to be fixed.
Comment 3 Shawn W Dunn 2023-05-31 14:24:31 UTC 
(In reply to Nate Graham from comment #2)
> Sounds like a driver bug. Not sure how we could fix this ourselves in KWin.
> Would it be possible to detect that there's no output and try to switch to
> 24-bit mode? If not, we probably have to wait for the driver bug to be fixed.

*shrug*  I wasn't sure where the bug actually was, or if this is something that can be "fixed" via kwin or not.   It appears that the proximal cause is in the amdgpu drm driver.