Version: (using KDE 4.4.0) OS: Linux Installed from: Ubuntu Packages On my laptop, on which the screen resolution is 1366x768 and the panel is maximized, the first character of the digital clock is always at least partially cut off, at times resulting in the time being unreadable (doesn't happen on my desktop, with a resolution of 1920x1080). Been seeing this since ~ early 4.3.
I have the same problem. At first it was only that the first character was missing, now the digital clock is totally unreadable when I start KDE. Starting digital clock settings and simple klicking Ok makes the clock render correctly, and it stays that way until the next login or reboot (see screenshots). My screen resolution is 1920x1200. I'm using KDE 4.4.1 from the Ubuntu repositories now, but I had the same issue with older versions.
Created attachment 41326 [details] The unreadable clock
Created attachment 41327 [details] The normal clock, after I visited Digital Clock Settings (probably not that interesting...)
I have the same problem as #1 with KDE 4.4.2-1 from Debian experimental.
I have same problem in fedora 13 (notebook Lenovo T400) and Kubuntu 10.04 (netbook HP mini) .
Created attachment 47413 [details] it supposes to be 10:42 am
Created attachment 48444 [details] last chars cut In my case last chars are cut when using a custom font. KDE 4.4 don't adjust the font size automatically any more as it was in 4.3
Is this still a problem >= KDE 4.5?
*** Bug 249699 has been marked as a duplicate of this bug. ***
*** Bug 254161 has been marked as a duplicate of this bug. ***
*** Bug 254438 has been marked as a duplicate of this bug. ***
*** Bug 254439 has been marked as a duplicate of this bug. ***
*** Bug 258077 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > Is this still a problem >= KDE 4.5? Yep, still happens in 4.6.3.
Note that bug 258077 comment 2 contains steps to reproduce the bug (however, I haven't checked them against a newer KDE SC installation ...)
I solved this problem in my computer doing: in system settings>locate>time & date: in time format, click inside the box, put some space between "SS" and "AMPM" and then delete AMPM. Works for me, maybe help.
Created attachment 60775 [details] click inside the box, put some space between "SS" and "AMPM"
Created attachment 60776 [details] result
(In reply to comment #18) > Created an attachment (id=60776) [details] > result While that does "solve" the problem, it's hardly a very practical workaround. All that extra space is wasting a lot of pixels on the panel (not to mention it looks awful). Also, as silly as it sounds, the time without the AM/PM just doesn't look right to me. I'm much more content doing these steps once per log-in: right-click the clock -> Digital Clock Settings (or Adjustable Clock Settings, as this bug affects that widget as well) -> OK -> left-click the clock... But I guess for someone that doesn't care about my little nit-picks, yours is a viable solution. :) On a side-note/bitchy rant/tangent, it's really hard for me to believe this bug still exists a full year and three months after being reported. For all the amazing and complex things Plasma can do, how is it that properly displaying the time presents it with such difficulty?
In my computer, the problem can be worked around by just adjust the height of the task bar bigger. (If you can't reprocedure this, you can try to adjust it smaller) Since clock is essential for most user's system, maybe the developer can put a little more attention to this bug? This bug has lasted for 2 years.
I'm using Debian Testing with KDE 4.11 and I noticed that the 1st digit is cut off when using non-default fonts system-wide (e. g. Droid instead of Deja Vu). After reverting the settings for fonts in systemsettings, the problem is gone for me. Might be related to font rendering in Linux, the widget seems to fail to update its width _properly_.
Here is my review request on this bug: https://git.reviewboard.kde.org/r/115431/ I have almost forgotten this.
Can confirm this is still happening on KDE 4.14.2 - with higher font DPI, the problem is even worse (at 120dp instead of the default 96, the AM/PM bit is chopped off altogether).
Created attachment 90508 [details] Panel clock (96dpi, DejaVu Sans Regular)
Created attachment 90509 [details] Panel clock (120dpi, DejaVu Sans Bold)
Created attachment 90510 [details] Panel clock (96dpi, DejaVu Sans Regular) Uploaded wrong image, this is the correct 96dpi version.
Hello! 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! Nate Graham
and this is why I've abandoned KDE On Fri, Jun 8, 2018 at 1:28 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=228902 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |UNMAINTAINED > Status|CONFIRMED |RESOLVED > > --- Comment #27 from Nate Graham <nate@kde.org> --- > Hello! > > 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! > > Nate Graham > > -- > You are receiving this mail because: > You are on the CC list for the bug.