| Summary: | KScreenLocker shows time in UTC for Kazakhstan time zones | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreenlocker | Reporter: | Zhanibek Adilbekov <zhanibek.adilbekov> |
| Component: | greeter | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | bshah, mgraesslin, sj2000, stupor_scurvy343 |
| Priority: | NOR | ||
| Version First Reported In: | 5.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| URL: | https://bugreports.qt.io/browse/QTBUG-53071 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Zhanibek Adilbekov
2016-04-29 00:02:27 UTC
How did you do step 3? The lockscreen should follow the global time zone data. Though it might be required to restart the session. I can confirm this issues with Kazakhstan cities time zones. After updating to timezone-data-2016d I have strangeness with time settings in plasma 5 for any Kazakhstan cities. My timezone is Asia/Oral The system show correct time: $date Sat Jul 2 00:26:31 +05 2016 Plasma clock widget show 2:26pm. But when I click to "Adjust Date and Time" in "Date and Time" tab displayed correct time, local timezone is correct Asia/Oral. When I lock screen I see 7:26pm. So at the moment I have 3 different time: 2:26pm -5 GMT in the plasma clock widget 0:26am +5 GMT in the system (correct) 7:26pm GMT in the Breeze lock screen and sddm. For testing I change timezone settings to Asia/Almaty and Asia/Aqtau and got same results - 3 different time. According changes logs for timezone-data-2016d : https://mm.icann.org/pipermail/tz-announce/2016-April/000038.html "Many corrections to historical time in Kazakhstan from 1991 through 2005. (Thanks to Stepan Golosunov.) Replace Kazakhstan's invented time zone abbreviations with numeric abbreviations." So seems replacing zone abbreviation with numeric in LMT is affected to the plasma. According to $URL, this was a bug in Qt. |