GNOME Bugzilla – Bug 523686
World Clock Applet Uses Wrong Timezone Data
Last modified: 2008-04-09 01:48:29 UTC
Please describe the problem: I'm living in UTC+8 timezone (no DST) and I added Austin, Texas in World Clock Applet (in DST after middle of March). Due to DST, Austin, Texas should be UTC-5 now, but the applet showed wrong time for Austin (still UTC-6). Steps to reproduce: 1. Added Texas, Austin into "Locations" of GNOME Applet Actual results: The time of Austin was wrong. Expected results: The time of Austin should be shown with DST considered. Does this happen every time? Yes Other information:
Created attachment 107727 [details] Screenshot of wrong time of Austin, Texas When London (with UTC) was at 08:09 AM of Mar 21, Austin should be at 03:09 AM, but 02:09 AM was shown in the screenshot.
What was the timezone set for Austin? Maybe the wrong one was automatically chosen?
Created attachment 108781 [details] Screenshot of wrong time of Austin, Texas The time of Austin displayed in World Clock Applet was different from the time displayed by tzselect.
(In reply to comment #2) > What was the timezone set for Austin? Maybe the wrong one was automatically > chosen? Sorry that I'm not sure about what information you need. I ran tzselect on Mar 21st and compared the time shown with the time displayed in Clock applet, as in the attachment I've just upload. They were different. So it seems to me that the World Clock Applet was _not_ using timezone information as stored in tzdata. Oddly enough, the time of Austin shown is correct on Apr 7th, as CDT (UTC-5). But after I set system time to Mar 21, it was wrong again (showed CST, UTC-6). So I concluded that the World Clock Applet does support DST, but just uses wrong timezone data. And I corrected the Summary of this bug accordingly. BTW: tzselect is the timezone list applet used in Debian and derived distros. It reads (as to my understanding) timezone data from tzdata.
You can see the timezone used for Austin in the preferences dialog of the clock. What is it?
Oh, it's "America/Monterrey" for Austin! It is wrong. Monterrey is in Mexico who follows different DST from that of Austin. In Monterrey the CDT begins at the first Sunday of April. Therefore this explained this error. So I guess we can use the same way we solved bug 519823, that is to let the user choose the timezone rather than guessing it?
It's fixed in 2.22.1. *** This bug has been marked as a duplicate of 519823 ***
Yes, I'm running 2.22.1, seems OK now. Thanks!