Sydney timezone is in the wrong location

Bug #1172015 reported by Jackson Doak
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Confirmed
Medium
Unassigned
libtimezonemap (Ubuntu)
Confirmed
Medium
Unassigned
ubiquity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

In ubiquity, the timezone marker points at least 500km away from sydney. it seems to be in the ACT(canberra) rather than new south wales.

This occurs when choosing the location in the drop down list.

Revision history for this message
Jackson Doak (noskcaj) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1172015

tags: added: iso-testing
Revision history for this message
Sergio Meneses (sergiomeneses) wrote :

I got this picture using Ubuntu-Saucy

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Jackson Doak (noskcaj) wrote :
Revision history for this message
Timothy Arceri (t-fridey) wrote :

I too as an Australian have noticed this in the past. Looking at the Ubiquity source the code that produces these locations is in: ubiquity/tz.py

It processes the locations from the file /usr/share/zoneinfo/zone.tab which is from the Unix tz database and looking at the file on my 13.04 system it seems the Sydney location is pretty much correct: -33.52 +151.13. Its possible that the code that parses the locations isn't working correctly. Are there other citys around the world in the wrong place or is it just Sydney?

Changed in hundredpapercuts:
status: New → Confirmed
Revision history for this message
Jackson Doak (noskcaj) wrote : Re: [Bug 1172015] Re: Sydney timezone is in the wrong location

Interesting.

I say it's a conspiracy against sydney ;) because bug 1066223 also exists

On Fri, May 10, 2013 at 11:55 PM, Timothy Arceri <<email address hidden>
> wrote:

> I too as an Australian have noticed this in the past. Looking at the
> Ubiquity source the code that produces these locations is in:
> ubiquity/tz.py
>
> It processes the locations from the file /usr/share/zoneinfo/zone.tab
> which is from the Unix tz database and looking at the file on my 13.04
> system it seems the Sydney location is pretty much correct: -33.52
> +151.13. Its possible that the code that parses the locations isn't
> working correctly. Are there other citys around the world in the wrong
> place or is it just Sydney?
>
> ** Changed in: hundredpapercuts
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172015
>
> Title:
> Sydney timezone is in the wrong location
>
> Status in One Hundred Paper Cuts:
> Confirmed
> Status in “ubiquity” package in Ubuntu:
> Confirmed
>
> Bug description:
> In ubiquity, the timezone marker points at least 500km away from
> sydney. it seems to be in the ACT(canberra) rather than new south
> wales.
>
> This occurs both with auto-locate and when manually selecting the
> location.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hundredpapercuts/+bug/1172015/+subscriptions
>

Changed in hundredpapercuts:
milestone: none → papercuts-s-ubiquity
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libtimezonemap (Ubuntu):
status: New → Confirmed
tags: added: saucy
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Brian Murray (brian-murray) wrote :

My testing seems to indicate that the location of the marker is dependent upon where you click. So if you move your cursor around just a wee bit the city name will stay the same although the pushpin marker has moved on the map.

This may be more noticeable with Anchorage, AK or Honolulu, HI.

Revision history for this message
Jackson Doak (noskcaj) wrote :

The issue is that when selecting the place from a drop down it doesn't
default to the actual location of the place, just the state it's in

On Fri, Jun 28, 2013 at 6:12 AM, Brian Murray <email address hidden> wrote:

> My testing seems to indicate that the location of the marker is
> dependent upon where you click. So if you move your cursor around just
> a wee bit the city name will stay the same although the pushpin marker
> has moved on the map.
>
> This may be more noticeable with Anchorage, AK or Honolulu, HI.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172015
>
> Title:
> Sydney timezone is in the wrong location
>
> Status in One Hundred Paper Cuts:
> Confirmed
> Status in “libtimezonemap” package in Ubuntu:
> Confirmed
> Status in “ubiquity” package in Ubuntu:
> Confirmed
>
> Bug description:
> In ubiquity, the timezone marker points at least 500km away from
> sydney. it seems to be in the ACT(canberra) rather than new south
> wales.
>
> This occurs both with auto-locate and when manually selecting the
> location.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hundredpapercuts/+bug/1172015/+subscriptions
>

Revision history for this message
Brian Murray (brian-murray) wrote :

I'll update the description with this information then Jackson.

description: updated
Changed in libtimezonemap (Ubuntu):
importance: Undecided → Medium
description: updated
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

This happens also on trusty with ubiquity 2.17.0.
As Brian wrote in comment #9 different locations are affected. In Asia the issue is more clear. Try it with Yecatarinburg. A tag for trusty will be added.

tags: added: trusty
Changed in hundredpapercuts:
importance: Undecided → Medium
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
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.