SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Use the digital clock widget on your taskbar 2. Use the task manager/icons-only taskbar on the same bar. 3. Open an application that displays the number of unread notifications in its icon on the taskbar, for example Telegram. 4. Wait for notifications to come in on that application. OBSERVED RESULT The number on the application icon will sometimes display simple block characters instead of the actual numbers. Whenever this happens, the numbers in the digital clock widget will also be replaced by block characters. This mostly happens when the number on the application icon reaches two or three digits. Reading those notifications refreshes the numbers and brings them back to being displayed normally. EXPECTED RESULT All numbers should be rendered normally on the taskbar and digital clock widget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Tested with Breeze Dark theme and symbol theme and Source Code Pro 10pt font.
Can you attach a screenshot that shows the issue?
(In reply to Nate Graham from comment #1) > Can you attach a screenshot that shows the issue? Yes, I will do that as soon as the bug pops up again. It happens randomly.
Created attachment 145457 [details] KDE Taskbar/panel where the digital clock widget only displays the time correctly; the date has been replaced with block characters Here is a screenshot of the taskbar showing the bug. Note that contrary to my initial post, Telegram is not running here. Opening Telegram and having it display the number of notifications in the icon actually reset the digital clock widget and had it display the date correctly.
Oh, this. :/ Does it happen when you resume the machine from sleep? Do you have an NVIDIA GPU?
(In reply to Nate Graham from comment #4) > Oh, this. :/ > > Does it happen when you resume the machine from sleep? > > Do you have an NVIDIA GPU? I cannot comment on the sleep function since I don't use that. And yes, I am using a Geforce 1050 Ti.
I think we have a bug report tracking this, but I can't find it. We can use this for now.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Additional info: I recently got a new AMD GPU instead of the Nvidia one, installed the appropriate drivers and the error still persists.
The issue is either in the GPU drivers for *both* GPUs, or else deep in Qt. Either way not a KDE bug, but I don't know which of those it might be, so I'll keep this open for now.