Issue in Time Zone Database for Kazakhstan's zones
After upgrading tzdata to 2016d version some of applications unable to determine right timezone for all zones which belong to Kazakhstan. I personally use Asia/Almaty (which is +06:00 and no DST) on my machine (Arch Linux with Plasma 5.6), and it leads some programs to produce unexpected results. E.g.: Digital Clock applet shows -12 hours from current time and Plasma Lockscreen shows time in UTC. I tried downgrade to 2016c and it works just fine. Please fix the issue, or at least return to previous state (which worked fine). Thanks! -- Best regards, Zhanibek Adilbekov. Tel: +7 707 817 5253 Skype: zhanibek.adilbekov Email:zhanibek.adilbekov@gmail.com zhanibek.adilbekov@live.com liljay.it@gmail.com
On 04/28/2016 04:15 AM, Zhanibek Adilbekov wrote:
After upgrading tzdata to 2016d version some of applications unable to determine right timezone for all zones which belong to Kazakhstan. I personally use Asia/Almaty (which is +06:00 and no DST) on my machine (Arch Linux with Plasma 5.6), and it leads some programs to produce unexpected results. E.g.: Digital Clock applet shows -12 hours from current time and Plasma Lockscreen shows time in UTC.
I'm not observing this problem on Fedora 23 (2016d-1.fc23) with gnome-clocks (3.18.0-1.fc23). Other users have reported problems with the Plasma Digital Clock applet after earlier tzdata upgrades. See for example: https://bbs.archlinux.org/viewtopic.php?id=193233 https://bugs.kde.org/show_bug.cgi?id=343610 https://www.kubuntuforums.net/showthread.php?69655-Issues-with-Plasma-Digita... The first thread says that a relevant bug was fixed in plasma 5.5; are you running that version? If not, I suggest upgrading. If so, perhaps there are other, similar bugs that haven't been fixed yet.
I looked at this <https://github.com/eggert/tz/commit/8ee11a301cf173afb0c76e0315b9f9ec8ebb9d95> commit, which adjusts some transitions for KZ. After looking closer to diffs I found out that formats of zones are changed, e.g. for Asia/Almaty it changed from ALMT to +06. I'm not familiar with TZ files, but I suppose this changes are the reason of incompatibility for some apps. On 28.04.2016 22:48, Paul Eggert wrote:
On 04/28/2016 04:15 AM, Zhanibek Adilbekov wrote:
After upgrading tzdata to 2016d version some of applications unable to determine right timezone for all zones which belong to Kazakhstan. I personally use Asia/Almaty (which is +06:00 and no DST) on my machine (Arch Linux with Plasma 5.6), and it leads some programs to produce unexpected results. E.g.: Digital Clock applet shows -12 hours from current time and Plasma Lockscreen shows time in UTC.
I'm not observing this problem on Fedora 23 (2016d-1.fc23) with gnome-clocks (3.18.0-1.fc23).
Other users have reported problems with the Plasma Digital Clock applet after earlier tzdata upgrades. See for example:
https://bbs.archlinux.org/viewtopic.php?id=193233
https://bugs.kde.org/show_bug.cgi?id=343610
https://www.kubuntuforums.net/showthread.php?69655-Issues-with-Plasma-Digita...
The first thread says that a relevant bug was fixed in plasma 5.5; are you running that version? If not, I suggest upgrading. If so, perhaps there are other, similar bugs that haven't been fixed yet.
-- Best regards, Zhanibek Adilbekov. Tel: +7 707 817 5253 Skype: zhanibek.adilbekov Email:zhanibek.adilbekov@gmail.com zhanibek.adilbekov@live.com liljay.it@gmail.com
On 2016-04-28 05:15, Zhanibek Adilbekov wrote:
After upgrading tzdata to 2016d version some of applications unable to determine right timezone for all zones which belong to Kazakhstan. I personally use Asia/Almaty (which is +06:00 and no DST) on my machine (Arch Linux with Plasma 5.6), and it leads some programs to produce unexpected results. E.g.: Digital Clock applet shows -12 hours from current time and Plasma Lockscreen shows time in UTC. I tried downgrade to 2016c and it works just fine.
Please fix the issue, or at least return to previous state (which worked fine). Thanks!
Suggestions from previous plasma digital clock bug reports: - Reapply 2016d. - Check /etc/localtime links to or cmp to Asia/Almaty, and you have exported TZ=Asia/Almaty or TZ is unset. - Check date -u, date, timedatectl, and hwclock output. - Check time on analogue or another desktop clock app. - Change your digital clock app local timezone to something else, check times, then change it back and check times. Report upstream bug against clock app(s)! These apps do not seem to handle DST transitions or time zone changes properly. Closing and relaunching the app or desktop may also make the problem go away until the next change. In general: suspect your own code before apps, and apps before infrastructure, unless you can show the same symptom appears in multiple apps. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
participants (3)
-
Brian Inglis -
Paul Eggert -
Zhanibek Adilbekov