Bug 473736

Summary: Serious rendering glitches render the Plasma Wayland desktop unusable when trying to customize the desktop (multi-gpu desktop system)
Product: [Plasma] plasmashell Reporter: Neal Gompa <ngompa13>
Component: generic-multiscreenAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol, nate, nicolas.fella, notmart, xaver.hugl
Priority: NOR    
Version First Reported In: 5.27.7   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Neal Gompa 2023-08-25 01:27:46 UTC
SUMMARY
When trying to use KDE Plasma Wayland on a system that has two GPUs (primary NVIDIA RTX 2060, secondary AMD Radeon HD 6790) in a multi-monitor setup (primary monitor on the NVIDIA card, two secondary monitors on the AMD card), the desktop starts tearing, glitching out, and having severe rendering bugs when doing various actions, particularly when trying to customize the Plasma desktop itself.

(NOTE: I am reporting this bug on behalf of another who is unable to report the bug directly.)


STEPS TO REPRODUCE
1. Attempt to customize the panel
2. Attempt to change the global theme

OBSERVED RESULT
Plasma completely spazzes out in a way that makes it unusable.

Video clip demonstrating this (shared with permission, epilepsy warning due to heavy flickering and glitching): https://ngompa.fedorapeople.org/bugs/pxl-capture-tobin-f38-plasma-wayland-glitchfest.webm

EXPECTED RESULT
Plasma should behave normally and allow regular usage.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 38 (KDE Plasma)
(available in About System)
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109
Qt Version: 5.15.10

ADDITIONAL INFORMATION
This generally works properly on X11 according to the user, so I'm pretty sure this has something to do with how we handle multi-GPU stuff.
Comment 1 Zamundaaa 2023-08-28 19:16:11 UTC

*** This bug has been marked as a duplicate of bug 467771 ***
Comment 2 Nate Graham 2023-08-28 19:27:23 UTC

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