** Changed in: gnome-panel
Importance: Unknown = Medium
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Northern Idaho in the US in in the pacific timezone (America/LosAngeles), see
http://www.law.cornell.edu/uscode/15/usc_sec_15_0264000-.html
I noticed the problem for Moscow, Idaho, US.
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
** Changed in: gnome-panel
Status: New = Fix Released
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
the bug has been fixed upstream now
** Changed in: gnome-panel (Ubuntu)
Status: Triaged = Fix Committed
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of
OK... so it is now possible to set my local timezone (St Petersburg,
Florida) correctly, but the second timezone I have configured (London,
UK) is still showing up as BST + 5 even after manually selecting
Europe/London as the timezone... Surely (since the UK has now changed
for the summer) it
Upstream means fixed in GNOME's subversion, so it's not fixed yet in
Ubuntu.
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
On Mon, Apr 07, 2008 at 03:58:39PM -, Richard J Foster wrote:
OK... so it is now possible to set my local timezone (St Petersburg,
Florida) correctly, but the second timezone I have configured (London,
UK) is still showing up as BST + 5 even after manually selecting
Europe/London as the
Ah... Thanks Steve. As long as that's the way it's supposed to work. I
had briefly looked at the patch in GNOME's repository and couldn't see
how it might fix that apparent weirdness, but unfortunately I didn't
have the resources (or time) to build things locally and check for
myself.
From my
This bug was fixed in the package gnome-panel - 1:2.22.1-0ubuntu1
---
gnome-panel (1:2.22.1-0ubuntu1) hardy; urgency=low
* New upstream version:
Panel
- Convert username/login to UTF-8 in logout dialog
- Fix applet processes not quitting when the applet is removed (lp:
This bug should really be addressed one way or another for 8.04. The
consequences of relying on gnome-panel to choose the right time zone for
you are potentially quite unfortunate.
Sebastien, what's your opinion on #199644 as a preliminary fix for this?
I still believe that the current behavior
I don't think fixing bug #199644 will make a real difference for this
one, most people pick a city because that's the first choice and they
want to get weather informations
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You
A patch to simply stop the automatic timezone selection would be quite
easy. I can do this if it is needed.
Alternatively, I can improve my original patch to allow for timezones to
be specified for entire countries/states. This would probably also be
rather easy, though it would require that
On Thu, Apr 03, 2008 at 09:06:02PM -, Sebastien Bacher wrote:
I don't think fixing bug #199644 will make a real difference for this
one, most people pick a city because that's the first choice and they
want to get weather informations
I don't agree. I think a clock is a much more basic
you have a point there, the timezone should be the first thing selected
and the weather station should be an option but the issue is mainly the
wrong timezone mapping, once that was fixed selecting a city should work
alright.
The upstream bug has some first round of patches, one to workaround the
** Description changed:
- I went to the preferences panel of GNOME's clock applet to add a
- location. However, when I went to add Pittsburgh, it associated the
- city with the America/Detroit timezone when it belongs America/New York
- timezone. The latitude and longitude are correct.
+ The
** Description changed:
The gnome panel clock applet's Locations section assigns the wrong
timezone to many cities if you add them via Edit - Add - Find.
Examples of cities that have the wrong timezone assigned include
Pittsburgh USA, Beijing China, Bombay (Mumbai) India, St. Petersburg
San Antonio, TX and Killeen, TX are also incorrect. It selects
America/Monterrey, which is not the same TZ.
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Same thing for me : France/Paris
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Tags added: metabug
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Tags removed: metabug
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Okay but first you need to map the cities to the countries
I am guessing this would do the job
http://www.geodatasource.com/cities-free.html
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification
The Slovakian city Kosice according to gnome calendar is in
Europe/Uzhgorod timezone. What is wrong.
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
There is no need in listing cities that are wrong.
Almost all cities are incorrect, as the timezone that is nearest the
position of the city is selected, not the one the place is really in.
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
Yeah, In my solution I didn't mean that you'd need to document each
city's timezone -- only if there was something unique about it... you
should be able to just map countries and potentially states / regions of
countries... *IF* you needed anything at all.
Ryan
--
Clock applet chooses wrong
Hm. But surely we must have a definite database. I guess it is somewhere
at Nasa or google maps maybe...
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Russia, Saratov. We have Europe/Samara but this value is wrong. Right value is
Europe/Moscow.
I guess many other locations will have wrong TZ in every country...
I can agree with Simos, but now in beta I see chooser... It's huge list!
May be just limit to calculated TZ as pre-selected value and
According to Wikipedia there are 245 political entities in the world...
http://en.wikipedia.org/wiki/List_of_countries
... and only 193 with general international recognition
So we've got 24 time zones...
A little history:
In 1878, Sir Sandford Fleming (1827–1915) developed the system of
I would say that this issue will lead to embarrassing negative
publicity, because it is common with neighboring countries to have some
sort of animosity; seeing the timezone of some other country when you
select your city is going to be bad.
What I recommend is to disable the auto-calculation of
I registered a bug on this when I couldn't find this one... bug # 199976
I know this has all been rehashed, but I think trying to add location /
TZ data for each location entry is not going to work because the system
doesn't select a location entry with the proper timezone in the first
place.
I
The obvious way to fix this would be to add a timezone entry to each
city in Locations.xml. Unfortunately, that would be a very tedious task.
It may be better to add timezone information to locations where the
distance code gives the incorrect result, and use the distance code as a
default.
--
** Attachment added: Patch for libgweather
http://launchpadlibrarian.net/12714304/libgweather-tzfix.diff
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of
These two patches (for gnome-panel and libgweather trunks) may or may
not lay the groundwork for solving this problem. As I proposed in my
recent comment, the code allows for timezone tags in Locations.xml;
I've added an example for San Diego.
Unfortunately, I can't figure out how to test this,
Of course, it is almost impossible to write code that works perfectly
without any testing. The patches here should now work.
I'm not happy with this solution, however. It seems as though it
requires a huge amount of work in updating Locations.xml, in a rather
unfortunate way. It could certainly
I still believe the correct solution for hardy is to not infer a
timezone based on the city coordinates at all, and instead fix the
timezone selector. Trying to get correct timezone settings for all
locations is going to take a lot of time and effort - relying on this
means we will still have
I agree that the solution is rather wanting, and believe that the
timezone-guessing code is something that does not belong in any release.
The idea of it not selecting a timezone at all is interesting: it would
be very easy to do - I can make the patch if necessary - and wouldn't
require any extra
** Tags removed: metabug
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Summary changed:
- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, St
Petersburgh, Beijing)
+ Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
For triagers: duplicates of this bug are frequently being filed against
tzdata.
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Tags added: metabug
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
39 matches
Mail list logo
