GNOME Bugzilla – Bug 574219
should use GNOME home time zone for calendar and invitations
Last modified: 2010-10-29 13:19:53 UTC
Please describe the problem: I just flew in to Hong Kong for the week. I clicked on the clock, added Hong Kong as a location, clicked on the home button, and now my system time is Hong Kong UTC+8. This is reflected by both the clock applet and the date command. I just got an appointment invitation by mail. I was very surprised by the time, then I realized it was still showing the time in my old home time zone, rather than my current time zone. Evolution should definitely use the same time zone rather than making me change it there too. Steps to reproduce: 1. Add a timezone (Clock Applet->Preferences->Locations->Add->Hong Kong) 2. Set Hong Kong as your home time zone Clock Applet, scroll to HOng Kong, click the Set button) Actual results: Everything thinks I'm in Hong Kong except evolution. Expected results: Everything thinks I'm in Hong Kong (i.e. Evolution uses the currently selected GNOME time zone). Does this happen every time? Yes. Other information: There must be a bug for this already, but if there is, I can't find it.
It's only for the calendar and invitation mails (iTIP formatter?). Incoming mails already display the correct local time in the header pane. So in the below example, I expect the Start and End times to be 06:00 PM and 06:30 PM. <NAME> requests your presence at the following meeting: <TITLE> Location: <LOCATION> Start time: Tomorrow 9:00 PM End time: Tomorrow 9:30 PM When: Friday, 6 March 2009 6:00 PM-6:30 PM (GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi Where: <LOCATION> *~*~*~*~*~*~*~*~*~*~*
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 544187 ***
Hi Andre Thanks, but I don't think it's a dupe of that one. That one is a crasher bug.
Ooops. I'm sorry.
Correct, this one is part of bug #381132. *** This bug has been marked as a duplicate of bug 381132 ***