Bug 495123

Summary: Panel has visual artifacts when translucent
Product: [Plasma] plasmashell Reporter: Anil <cd+kde>
Component: PanelAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: nate, niccolo.venerandi
Priority: NOR    
Version First Reported In: 6.2.1   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshot of the taskbar, showing visual glitches

Description Anil 2024-10-21 03:27:17 UTC
Created attachment 175071 [details]
Screenshot of the taskbar, showing visual glitches

SUMMARY
When there is any application that is maximized, or underlaps the bottom panel (taskbar) the panel displays normally. However, if there are no windows at all, (or it's a floating window that doesn't cause any overlapping), the entire panel has bad visual glitches

STEPS TO REPRODUCE
1. This is maybe? related to launching a steam game in full screen then exiting. Will have to do more tests to see
2. Close all applications (or reposition them to be floating and not overlapping the panel)

OBSERVED RESULT
The entire taskbar panel is badly glitched


EXPECTED RESULT
The transparency behavior works correctly


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: Framework
Product Name: Laptop
System Version: A3

ADDITIONAL INFORMATION
Comment 1 Anil 2024-10-21 03:29:10 UTC
Workaround: Set the panel to always be opaque, instead of adaptive or translucent. (My guess is this has something to do with the blending)
Comment 2 Anil 2024-10-21 05:09:55 UTC
Okay, yes this requires launching a steam game fullscreen first. From that point onwards, the glitching exists until reboot.
Comment 3 Nate Graham 2024-12-12 20:35:08 UTC
This is a graphics driver bug; please read https://docs.mesa3d.org/bugs.html and submit a bug report for the Mesa developers. Thanks!