See the screenshot. The issue does not occur when setting the clock to display the US Eastern time zone (same as my system setting) instead of the Local option. Reproducible: Always Steps to Reproduce: 1. Add a Digital Clock widget. Actual Results: Time is wrong. Expected Results: Time is right.
Created attachment 101508 [details] Screenshot of issue.
Also see these similar bugs: https://bugs.kde.org/show_bug.cgi?id=363597 (resolved: user chose wrong time zone) https://bugs.kde.org/show_bug.cgi?id=332851 (unconfirmed: something strange in KDE4) https://bbs.archlinux.org/viewtopic.php?id=193233 (something similar solved in Plasma 5.5)
Can you also include your ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Created attachment 101509 [details] As requested!
selectedTimeZones=America/New_York Apparently you've set the clock to show you new_york as the timezone and not local
Edit, just re-read your first comment. >The issue does not occur when setting the clock to display the US Eastern time zone (same as my system setting) instead of the Local option. So this config is with you doing the workaround, not the config for when it's broken?
Interesting, so even though "Local" is checked in the applet configuration window, it's not set to it in the configuration file? Weird. Also, why wouldn't they be the same? That's my system time zone, so either of them should show the same time...
Oh, no, I wasn't doing the workaround when I uploaded the configuration file. Maybe the applet and its configuration file were out of sync since I changed
Oh, no, I wasn't doing the workaround when I uploaded the configuration file. Maybe the applet and its configuration file were out of sync since I changed them to test the workaround recently?
It also happens with a new instance of the clock (which defaults to the broken "Local" time zone setting). In addition, the numbers on the clock tend to disappear after a reboot or two, leaving only the separators. (Previously, just the date disappeared and the time remained, but this time the time disappeared too.)
See final comment in linked report *** This bug has been marked as a duplicate of bug 370149 ***