Bug 22927

Summary: timezone-2018d-2.mga7 update causes empty plasma panel clock and drakclock does not take timezone into account
Product: Mageia Reporter: Jüri Ivask <jyri2000>
Component: RPM PackagesAssignee: Base system maintainers <basesystem>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: basesystem, kde, mageiatools, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: timezone-2018d-2.mga7.src.rpm CVE:
Status comment:

Description Jüri Ivask 2018-04-19 08:45:20 CEST
Description of problem: timezone-2018d-2.mga7 update causes empty plasma panel clock and drakclock does not take account timezone


Version-Release number of selected component (if applicable): 2018d-2


Steps to Reproduce:
1. install timezone-2018d-2.mga7 update
2. note that Plasma Desktop panel clock is empty - no time there
3. launch drakclock and note that although timezone is set (here) to Europe/Tallinn it displays computer time (set to UT here) - timezone is not taken into account

Downgrade timezone (and timezone-java) packages to previous 2017b-1 version and the situation is OK again.
Comment 1 Marja Van Waes 2018-04-19 09:46:11 CEST
Only CC'ing KDE team now, I'll assign to the base system maintainers or to KDE team later (depending on whether I see something similar in Xfce after updating, or not)

CC: (none) => kde, marja11

Comment 2 Jüri Ivask 2018-04-19 09:59:40 CEST
Well - actually you can remove point 2 from my bug report as it is probably a result of point 3 - so to be more correct:

Steps to Reproduce:
1. install timezone-2018d-2.mga7 update
2. launch drakclock and note that although timezone is set (here) to Europe/Tallinn it displays computer time (set to UT here) - timezone is not taken into account
3. note that also Plasma Desktop panel clock is empty - no time there
Comment 3 Marja Van Waes 2018-04-19 11:15:49 CEST
I had misunderstood what you wrote about drakclock.


I cannot reproduce any of the issues here with Xfce and timezone Europe/Amsterdam. I only found it odd that, before testing, hwclock showed 2018-04-19 09:38:53.905550+02:00 which was one our behind the real time and also one hour behind the time that drakclock and the Xfce panel showed.

After changing my timezone to Europe/Talinn with drakclock, while selecting to use NTP and then closing drakclock and opening it again, Talinn time is still shown correctly. I've tried two different ntp servers, one close to you and one close to me, and both were good. After doing the above hwclock showed 
2018-04-19 12:04:51.655563+03:00 and after reverting to Europe/Amsterdam it 2018-04-19 11:08:06.702459+02:00.

It shows the same (apart from the minutes/seconds etc, of course), regardless of whether I tell drakclock that my system uses GMT time, or not.

I have no idea what happened on your system :-(

CC'ing mageiatools and basesystem maintainers.

CC: (none) => basesystem, mageiatools
Assignee: bugsquad => basesystem

Marja Van Waes 2018-04-19 11:16:14 CEST

Summary: timezone-2018d-2.mga7 update causes empty plasma panel clock and drakclock does not take account timezone => timezone-2018d-2.mga7 update causes empty plasma panel clock and drakclock does not take timezone into account

Comment 4 Jüri Ivask 2018-04-19 13:12:21 CEST
No ntp servers used here yet - just as time&date was set during install: hardware clock set to UT and local timezone Europe/Tallinn
Comment 5 Jüri Ivask 2018-04-19 13:38:02 CEST
Decided to try once more the timezone-2018d-2.mga7 update.

This time everything went OK - drakclock displayed local time according to the time zone and plasma panel clock was populated with correct local time.

No idea, what it was at first update...
Comment 6 Marja Van Waes 2018-04-19 16:22:59 CEST
(In reply to Jüri Ivask from comment #5)
> Decided to try once more the timezone-2018d-2.mga7 update.
> 
> This time everything went OK - drakclock displayed local time according to
> the time zone and plasma panel clock was populated with correct local time.
> 
> No idea, what it was at first update...

Thanks for the feedback.

I'll leave this report open for a while, in case someone else hits the same problem with this update, but let's set it to unconfirmed for now.

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 7 David Walser 2018-04-21 18:27:42 CEST
The bug was in the first attempted update to 2018d of this package which wiped out your /etc/localtime symlink.  It should be fine if you upgrade from the mga6 version to the current version now.

Resolution: (none) => FIXED
Status: UNCONFIRMED => RESOLVED