Bug 451914

Summary: [Wayland] Graphical glitches upon unlock with Multiple Monitors
Product: [Plasma] kscreenlocker Reporter: Matt <mattyhoffman7>
Component: greeterAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol, bhush94
Priority: NOR    
Version: 5.24.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Demonstration of 3 glitches occuring (artifacting, flickering/black screen, black screen flash)

Description Matt 2022-03-26 01:50:57 UTC
Created attachment 147733 [details]
Demonstration of 3 glitches occuring (artifacting, flickering/black screen, black screen flash)

SUMMARY
Occasionally I will experience graphical glitches upon unlocking my computer during the Wayland session if I have multiple monitors connected. I notice it the most after my computer has resumed from sleep, but have had it happen before that as well. Have noticed on both Tumbleweed and Arch using AMDGPU drivers.
The attached video shows 3 examples of the glitches I've experienced, they go away when I move the mouse over the space where the glitches are occurring.

STEPS TO REPRODUCE
1. Connect at least 2 monitors
2. Start a Wayland plasma session
3. Put the machine in suspend mode, then wake it up (might not be required, but I notice it most after suspend)
4. Unlock the Plasma Wayland session

OBSERVED RESULT
Occasionally there are graphical glitches (flickering, artifacting, etc.) on one or both of the screens

EXPECTED RESULT
Smooth unlocking process with no glitches

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.16.16-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz
Memory: 19.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

ADDITIONAL INFORMATION
Running Wayland with both screens at 1920x1080, 144Hz over DisplayPort. I have NOT observed this on X11 at all.
Comment 1 Aleix Pol 2022-09-20 00:27:56 UTC

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