Bug 496258

Summary: Volume/layout OSD is displayed in the top left instead of the center after an hour of use
Product: [Plasma] plasmashell Reporter: Greeniac <quarro>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, nate
Priority: NOR    
Version: master   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot shows the OSD in the top left.

Description Greeniac 2024-11-14 09:10:14 UTC
Created attachment 175805 [details]
Screenshot shows the OSD in the top left.

I've been getting this bug since updating to plasma 6.2.1*. Or a similar version.

SUMMARY
After boot, the volume/layout OSD is correctly displayed in the center. But after around an hour of use it starts to display in the top left of the screen. Without having to change the audio output as stated in other bug reports. The issue gets temporarily fixed by rebooting or by killing the plasmashell process.

STEPS TO REPRODUCE
1. Boot into KDE Plasma.
2. Use it normally for an hour or so.


OBSERVED RESULT
OSD is displayed in the top left of the screen.

EXPECTED RESULT
OSD being displayed in the middle of the screen.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7600K CPU @ 3.80GHz
Memory: 23.4 GiB of RAM
Graphics Processor: AMD Radeon Pro 580X
Manufacturer: Apple Inc.
Product Name: iMac18,3
System Version: 1.0

ADDITIONAL INFORMATION
I've gotten this bug in Fedora KDE and in Arch. I have gotten this bug with 2 displays and 3 connected (never tried with 1 ). I tried two different audio drivers. And it seems like this bug does not happen with a fresh install. Only happens after weeks of use. I do not do heavy customization. Just regular breeze with a different panel and color scheme.
Comment 1 Nate Graham 2024-11-14 18:30:06 UTC

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