Bug 462550

Summary: Sometimes single random digits of the Digital Clock disappear with AMD GPU
Product: [Plasma] plasmashell Reporter: postix <postix>
Component: Digital ClockAssignee: Plasma Bugs List <plasma-bugs>
Status: REPORTED ---    
Severity: normal CC: liemaeu, nate, postix
Priority: NOR    
Version: 5.26.3   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=365716
Latest Commit: Version Fixed In:
Attachments: Screenshot

Description postix 2022-12-02 14:28:15 UTC
Created attachment 154228 [details]
Screenshot

SUMMARY

Whoever took them, please hand them back and leave them where they belong! :)

STEPS TO REPRODUCE
1. Digital clock widget on the left non-primary screen in a dual screen set up
2. Just use the system as usual

OBSERVED RESULT
In general there's no issue, but every now and then, a single digit disappears, but may re-appear when the clock is updated again, i.e. time changes.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20221128
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.8-1-default (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon RX 580 Series
Comment 1 Nate Graham 2022-12-02 19:42:02 UTC
The NVIDIA version of this bug was supposedly fixed in Plasma 5.26; see Bug 365716. I guess there's still AMD left.
Comment 2 Richard Knausenberger 2022-12-15 08:38:31 UTC
Plasma 5.26.4, Nvidia, bug is still there. Switching to another font (e.g. Open Sans instead of the default Noto Sans) fixes it for me.

As far as I remember it only happened to the digital clock applet on my second screen desktop, never happened to the one in the panel of my main screen. Could also be because I show the date on my main screen one, but not on the desktop applet on my second screen. But I'm not sure.
Comment 3 Nate Graham 2023-02-05 03:56:27 UTC
This is going to end up being either an issue in KWin, or in the AMD graphics drivers. But almost certainly not in the Digital Clock code itself. Moving to KWin to start with.
Comment 4 Vlad Zahorodnii 2023-02-06 09:32:04 UTC
I'm pretty sure that's not a kwin bug. Use apitrace to debug whether it's a rendering issue in QtQuick first (comment 2 indicates that it might be a Qt bug); otherwise report to the driver developers.