The timer widget has visual problems when docked into a panel.
When I first add it, it looks all right. However, when after rebooting the system, the font will look very small. The problem disappears as soon as I resize the panel, and the font is displayed at the correct size.
I need to resize the panel every time I reboot my system in order to be able to read the figures of the timer.
Steps to Reproduce:
1. Add the timer widget to a panel.
2. Reboot the system or log out from KDE and then back in again.
The font of the timer look very, very small and almost illegible.
The font of the timer remains the same as when the timer was first docked into the panel.
Created attachment 80720 [details]
Screenshot showing the bug
do bugs get looked at at all?
On plasmashell 5.2.2 the timer only shows as icon in the panel and only expands on click to show (running) timers. I guess this bug can be closed.
Whether the timer should show in it's full form in panel I'm not yet sure about but if this is wanted a separate bug should be created imho.
Created attachment 105031 [details]
Bug screenshot, kubuntu 17.04
What widget is that? According to bug 353090, in Plasma 5 the timer widget only shows an icon instead of the remaining time in the system tray. This is because the system tray icon size is fixed.
I have the same issue on Plasma 5.12.5 with the Timer widget. The font size for the timer when placed in a panel is always extremely small due to vertical padding in the widget. It does not require a reboot as in the original bug report.
Steps to reproduce:
1. Add the timer widget to a panel. Font size is extremely small due to padding.
The font of the timer should be readable and roughly fit the height of the panel, like the Digital Clock widget.
Created attachment 112628 [details]
Screenshot of bug from Plasma Shell 5.12.5 on Arch Linux
This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.
Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting
If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging
Thanks for your understanding!