World clock times are incorrect

Bug #1199142 reported by Sam Bull
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Fix Released
High
Nekhelesh Ramananthan

Bug Description

The time right now is 9:42 pm. The clock shows the time as 22:42, which may just be the issue with the timezone (think there's another bug for that).

This is for my location (Brighton, UK), but other times being shown at 9:42 are:
Brighton: 10:42
Lyon: 11:34
Shoreham (which is down the road): 10:33
Firenze: 10:42

It appears as if the time is set based on position relative to your location or something weird like that, instead of using timezones. This means the clock times are basically nonsense.

Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

I need some information before confirming this bug. First did you set Brighton, UK as your current location by searching and adding it from the world clock list? By default, the clock app shows UTC time. I just tried adding Brighton, UK from the world clock list and it reports the correct time. I get positive results for Lyon, Shoreham and Firenze as well.

If they are off by few minutes, that is something that I anticipated before hand. Currently when you add a world clock, the time is fetched from using an online API and the time difference between that location and your current location is calculated and saved. This is then used to show times. This could result in it being off by few minutes sometimes.

The correct technical way of doing stuff is by using the timezone ID which for Brighton is Europe/London and the time should be displayed based on this. However at the moment Qt 5.0 does not have proper support for Timezones and hence does not use tzdata. Until this is resolved upstream there is nothing much I can do. If there is a better solution, feel free to explain and I can see if that can be implemented.

Changed in ubuntu-clock-app:
status: New → Incomplete
Revision history for this message
Sam Bull (dreamsorcerer) wrote :

Time for Brighton seems to be off by an hour, maybe it's ignoring DST.

So, this should be fixed when Qt 5 has timezones implemented properly? We should hold onto the bug report to make sure it's not forgotten then, but low priority.

Changed in ubuntu-clock-app:
status: Incomplete → Confirmed
Changed in ubuntu-clock-app:
importance: Undecided → High
milestone: none → coreapps-13.10-month-3
assignee: nobody → Nekhelesh Ramananthan (nik90)
Changed in ubuntu-clock-app:
milestone: coreapps-13.10-month-3 → coreapps-13.10-month-4
Revision history for this message
Sam Bull (dreamsorcerer) wrote :

Seems to be working correctly now.

Changed in ubuntu-clock-app:
status: Confirmed → Fix Released
Changed in ubuntu-clock-app:
milestone: backlog → hack-days-1309
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.