Digital clock widget show wrong time. My timezone is Asia/Sakhalin (UTC+11, MSK+8). date command in terminal show correct time: Sun Oct 23 18:52:35 +11 2016 But at the same time the digital clock widget placed on my panel shows 20:52 (difference is +2 hours). 'Adjust Date and Time' window shows correct time. It all started just a few releases ago (two or three). Before it everything was ok. I changed nothing in time/date. Reproducible: Always Steps to Reproduce: 1. Set timezone to Asia/Sakhalin. 2. Add Digital clock widget. 3. See the wrong time. Actual Results: Digital clock widget shows wrong time (+2 hours forward). Expected Results: Digital clock widget shows correct time (the same as 'date' command shows). plasma-workspace 4:5.8.2-0neon+16.04+build51 NAME="KDE neon" VERSION="5.8" ID=neon ID_LIKE="ubuntu debian" PRETTY_NAME="KDE neon User Edition 5.8" VERSION_ID="16.04" HOME_URL="http://neon.kde.org/" SUPPORT_URL="http://neon.kde.org/" BUG_REPORT_URL="http://bugs.kde.org/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial
Same here. It should be somehow connected with the recent changes in tzdata. tzdata-2016d source: Zone Asia/Sakhalin 9:30:48 - LMT 1905 Aug 23 9:00 - JCST 1937 Oct 1 9:00 - JST 1945 Aug 25 11:00 Russia SAK%sT 1991 Mar 31 2:00s # Sakhalin T 10:00 Russia SAK%sT 1992 Jan 19 2:00s 11:00 Russia SAK%sT 1997 Mar lastSun 2:00s 10:00 Russia SAK%sT 2011 Mar 27 2:00s 11:00 - SAKT 2014 Oct 26 2:00s 10:00 - SAKT 2016 Mar 27 2:00s 11:00 - SAKT tzdata-2016h source: Zone Asia/Sakhalin 9:30:48 - LMT 1905 Aug 23 9:00 - +09 1945 Aug 25 11:00 Russia +11/+12 1991 Mar 31 2:00s # Sakhalin T 10:00 Russia +10/+11 1992 Jan 19 2:00s 11:00 Russia +11/+12 1997 Mar lastSun 2:00s 10:00 Russia +10/+11 2011 Mar 27 2:00s 11:00 - +11 2014 Oct 26 2:00s 10:00 - +10 2016 Mar 27 2:00s 11:00 - +11 Looks like the applet has problems with format like this. I was able to 'fix' it by downgrading tzdata package to 2016d.
velifico@gmail.com Thank you! I just downgraded tzdata to 2016d-0ubuntu0.16.04 and everything get worked back.
Please see final comment in linked report *** This bug has been marked as a duplicate of bug 370149 ***