Bug 500061

Summary: Black screen when using dualmonitor on dedicated (AMD) gpu.
Product: [Plasma] plasmashell Reporter: Matej Starc <matej.starc>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: quarro
Priority: NOR Keywords: multiscreen, usability
Version First Reported In: git-stable-Plasma/6.3   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Matej Starc 2025-02-14 12:36:34 UTC 
SUMMARY
After update I am forced to use singlemonitor because if I try to login (or connect when already logged in) the second monitor, I get a black screen. I am fortunately able to go to another tty session. Do note that this started happening when I updated to the latest version.


STEPS TO REPRODUCE
1. Connect two monitors to (AMD?) gpu
2. Log in into your account
3. Observe the black screen

OBSERVED RESULT
Black screen on both screens then it cuts connection to both displays.


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.12.11-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 480 Graphics

ADDITIONAL INFORMATION
Monitor1: 1440p, 144Hz, 100% scale
Monitor2: 1080p, 144Hz, 100% scale
both have adaptive sync disabled, color profile set to "built-in", color accuracy: "prefer color accuracy".
Comment 1 Greeniac 2025-02-14 12:42:30 UTC 
Set color accuracy to prefer efficiency on both of your monitors and try again, i had this issue with prefer color accuracy with an AMD GPU.
Comment 2 Matej Starc 2025-02-14 20:08:10 UTC 
(In reply to Greeniac from comment #1)
> Set color accuracy to prefer efficiency on both of your monitors and try
> again, i had this issue with prefer color accuracy with an AMD GPU.

This seems to have fixed my issue.
Comment 3 Greeniac 2025-02-16 02:05:48 UTC 

*** This bug has been marked as a duplicate of bug 499789 ***