Bug 464493

Summary: Monitor is recognized by Plasma, but will not output anything on kwin wayland
Product: [Plasma] kwin Reporter: J <jandrewsternenberg>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: nate, xaver.hugl
Priority: NOR    
Version First Reported In: 6.1.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Monitor is identified correctly and enabled in this screenshot.
This is a picture of my monitor active yet still blank using kwin wayland

Description J 2023-01-19 09:20:50 UTC
Created attachment 155421 [details]
Monitor is identified correctly and enabled in this screenshot.

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Connect monitor to computer
2. Power on system
3. SDDM or LightDM greeter
4. Select Plasma
5. Login

OBSERVED RESULT
At login monitor displays greeter. Plasma starts, screen goes blank and stays blank

EXPECTED RESULT
At login monitor displays greeter. Plasma starts, screen turns on and stays on.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 6.1.6-arch1-3 (64-bit)
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
When logging into Plasma on X11 it will be enabled and display the desktop. When enabled on kwin wayland, the monitor goes blank and stays blank at login. I have to restart the machine once logged into wayland in order to get the monitor to display anything again.
Comment 1 Nate Graham 2023-01-23 21:16:25 UTC
To be clear, it's just that one monitor that stays black, and not all of them, right?
Comment 2 J 2023-01-24 17:43:39 UTC
(In reply to Nate Graham from comment #1)
> To be clear, it's just that one monitor that stays black, and not all of
> them, right?

Correct. The other two monitors are displaying mouse cursor, desktop, everything. The monitor is detected but will not display anything.
Comment 3 Nate Graham 2023-01-25 16:44:52 UTC
Cool, thanks.

Any chance you could test with the Plasma 5.27 beta? We fixed a ton of multimonitor issues for 5.27, and this might be one of them.

See https://community.kde.org/Plasma/Live_Images#Arch_with_kde-unstable_repository
Comment 4 J 2023-01-25 20:10:23 UTC
Unfortunately, I seem to only be able to install plasma 5.26.90. Except for the plasma-meta package which is on 5.27-1 which is okay. I can wait for Arch to update their repos. I will respond back when I am able to update all packages to 5.27?
Comment 5 Nate Graham 2023-01-25 20:21:06 UTC
5.26.90 is fine; that's current git master, AKA what will become 5.27.

5.26.80 is the beta version, if that's available.
Comment 6 J 2023-01-25 20:49:41 UTC
There has been no change in behavior of the display.
Comment 7 Nate Graham 2023-01-27 15:55:21 UTC
OK, thanks.
Comment 8 J 2023-01-28 11:44:07 UTC
Created attachment 155725 [details]
This is a picture of my monitor active yet still blank using kwin wayland

Here is a photo of my monitor detected, but still blank. When I use Spectacle, I can screenshot just this screen.
Comment 9 J 2023-01-28 11:47:53 UTC
If there is anythi(In reply to Nate Graham from comment #7)
> OK, thanks.

I really appreciate you taking the time to look into this, if there is anything I can provide to help further please don't hesitate to ask.
Comment 10 J 2024-08-02 17:14:10 UTC
Okay, I finally was able to acquire another machine to test this with. On Plasma 6+ Wayland it works with an intel HD 630 igpu using HDMI out. It does NOT work with my RX 6950 XT via HDMI or my RX 5700 XT via HDMI.
Comment 11 Zamundaaa 2024-08-05 21:06:58 UTC
Could you try setting the environment variable KWIN_DRM_PREFER_COLOR_DEPTH=24 for KWin, and see if it works then?
Comment 12 Bug Janitor Service 2024-08-20 03:47:25 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 13 J 2024-08-20 04:42:55 UTC
(In reply to Zamundaaa from comment #11)
> Could you try setting the environment variable
> KWIN_DRM_PREFER_COLOR_DEPTH=24 for KWin, and see if it works then?

This solution worked. I appreciate that.
Comment 14 J 2024-08-20 04:52:53 UTC
created an environment variable in ~/.config/plasma-workspace/env/ with the command:

export KWIN_DRM_PREFER_COLOR_DEPTH=24
Comment 15 Bug Janitor Service 2024-09-04 03:47:14 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 16 Zamundaaa 2024-09-05 12:23:20 UTC
Okay, if reducing the bpc works, then this is a driver bug (it's supposed to do that automatically). Please report this to https://gitlab.freedesktop.org/drm/amd/-/issues