Bugzilla – Bug 254525
US DST 2007 Timezone Changes not in Evolution
Last modified: 2007-08-22 06:45:40 UTC
Evolution apparently didn't switch over on March 11th to accept the new DST changes in the United States. Now calendar appointments are incorrectly persisted, and the running clock in the calendar component is off by an hour. I'm guessing this is related to http://bugzilla.gnome.org/show_bug.cgi?id=301363 and the iCal libraries (or something statically linked within Evolution) wasn't updated. I updated to the versions of Evolution & iCal in Factory-OSS, but it's still borked.
Created attachment 124384 [details] Screenshot of Calendar Errors Attached is the weirdness I'm seeing - noticed the calendar believes it is nearly 11:00, when in fact it's nearly 12:00.
Created attachment 125285 [details] Patch for New York only You can see additional bug reports: http://bugzilla.gnome.org/show_bug.cgi?id=417461 And Ubuntu's fix: https://launchpad.net/ubuntu/+source/evolution/+bug/91637 I had to manually hack & fix New York's timezone info file, which set the appropriate DST settings.
Created attachment 126525 [details] Sample meeting that is incorrectly added to Evolution Appointments are still not added correctly, even though Evolution's "clock" is now displaying the correct time. Accepting the attached appointment should schedule it for 9 AM, but instead it's added at 10 AM.
This appears to be a bug in the webdav module. If I accept the attached appointment (id=126525) into a webdavs folder via the Exchange connector, the time is an hour late. If I copy or accept the appointment into the native Evolution calendar on the file system then the correct hour appears. When I login to our OWA installation in a Web browser the appointment appears scheduled at the correct time. Additionally, if I create an appointment within Evolution itself things appear to work correctly. The appointment is scheduled at the correct time, copying to the local file system's calendar maintains the correct hour, and OWA shows the correct time in the browser. It appears the root of the cause is adding an appointment to a webdav calendar via e-mail.
John - Do you have the timezone update fix ? You can check by querying the changelog information, rpm -q --changelog evolution-data-server |less the following information should be appearing, * Thu Mar 08 2007 - pchenthill@novell.com bnc-251573-timezone-update.diff: Updates the timezone information. Also please run the following command. $find .evolution/exchange/ -name '*.ics' and send me the cache.ics for the particular calendar if possible. I want to check if the timezone present in the cache is the updated one.
Created attachment 127174 [details] Timezone records for my cache.ics I don't see the evolution-data-server fix - it doesn't appear that the update mirrors have it yet. I've been running YOU daily to check for updates and just applied the keyring fallback patch, but I currently don't see any updates for Evolution in YaST2. I can't attache the whole cache.ics file unfortunately (confidential corporate crapola), but I have attached the VTIMEZONE records for the cache.ics. If you'd like me to dig for other info (or work on stripping all the confidential stuff out) let me know. I removed & regenerated the cache.ics files, but the problem persisted. I also tried this on a brand-new install of Kubuntu Edgy Eft beta, and the same issue persists on their Evolution distro. The hour appears correctly, but appointments are added an hour late.
I have identified the issue. Its because a old meeting request sent from exchange is still using the wrong timezone information. The timezone information present in the cache is, BEGIN:VTIMEZONE TZID:(GMT-05.00) Eastern Time (US & Canada) X-MICROSOFT-CDO-TZID:10 BEGIN:STANDARD DTSTART:16010101T020000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=4 //* wrong information * END:DAYLIGHT END:VTIMEZONE The timezone present in the meeting sent is correct. Since the old and new timezones sent from exchange have same tzids and has no information to indicate the updated one. Have you run the migration tool on exchange server to migrate the timezones present in outlook calendar events ?
I have a thought about a solution for this issue. I will try to make out a patch soon.
I'm fairly sure they ran both the DST updater and the migration tool on the Exchange 2003 server... it appears things migrated & currently work fine on OWA and Outlook, just Evolution is skewed. Lookin' forward to the patch. Thanks!
Chen: Didn't you make a tool to migrate cache?
srini, the tool was made for the personal calendar. I have given a test build with the updated timezones and got the reply from the reporter as it fixed the issue. The update has been release for 10.2.