GNOME Bugzilla – Bug 558661
Incorrect time in google calendar
Last modified: 2009-09-07 10:33:20 UTC
I added google calendar to Evolutoin. My timezone in evolution is Asia/Kolkata. In google calendar, I have IST(GMT+05:30) which is same as Asia/Kolkata. I see that I see calendar events with 05:30 offset. For example, event is at 2:00 PM then I see it at 7:30 PM in evolution google calendar.
*** Bug 559744 has been marked as a duplicate of this bug. ***
Reproducible on 2.25 as well.
I can confirm this. I'm in PST which has a -8 time zone (set on both my computer and Google Calendar account) and events appear 3 hours early in Google Calendar if I create them through Evolution. I'm using Evolution 2.24.2 running on Ubuntu Intrepid 32-bit. Also, 563255 is another dupe of this from another user.
*** Bug 563255 has been marked as a duplicate of this bug. ***
Still present in nightly builds. In my case it shows version 2.26.0.
This is most annoying bug. Still present on 2.27.1.
Confirmed on Ubuntu 9.04, Evolution 2.26.1. I have also confirmed that Mozilla Lightning does NOT have this problem, which suggests this is not a Google display bug. My local system, Evolution calendar prefs, and Google calendar are all set to PDT. If I create an event on Google and sync to Evolution, it has the correct time. But if I create an event in Evolution and sync to Google, it shows up in Google 7 hours earlier than it should. It just so happens PDT is -7hrs from UTC. Seems the timezone adjustment is being applied twice somehow? I have exported, and have just attached, example VCALENDAR files from events created in Evolution, and in Lightning. Both were scheduled for 11am, the Lightning event showed on Google at 11am, the Evolution event showed (on the same Google calendar) at 4am. I can see a few syntax differences between the two, but I shouldn't go into further detail about that which I don't fully understand... Feel free to email me for further tests! I'd like to see this worked out (obviously).
Comment on attachment 134872 [details] Event created for 11am in Evolution BEGIN:VCALENDAR PRODID:-//Ximian//NONSGML Evolution Calendar//EN VERSION:2.0 METHOD:PUBLISH BEGIN:VTIMEZONE TZID:/freeassociation.sourceforge.net/Tzfile/America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:STANDARD TZNAME:PST DTSTART:19701101T010000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 END:STANDARD BEGIN:DAYLIGHT TZNAME:PDT DTSTART:19700314T030000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:http: //www.google.com/calendar/feeds/rgwin%40thefuelteam.com/private/full/(MANUALLYHIDDEN) DTSTAMP:20090518T024852Z DTSTART;TZID=/freeassociation.sourceforge.net/Tzfile/America/Los_Angeles: 20090518T110000 DTEND;TZID=/freeassociation.sourceforge.net/Tzfile/America/Los_Angeles: 20090518T120000 TRANSP:OPAQUE SEQUENCE:2 SUMMARY:this should be 11am PT DESCRIPTION:sdfhsdf CLASS:PUBLIC BEGIN:VALARM X-EVOLUTION-ALARM-UID:20090518T024906Z-4368-1000-1-118@monkey DESCRIPTION:this should be 11am PT ACTION:DISPLAY TRIGGER;VALUE=DURATION;RELATED=START:-PT15M END:VALARM END:VEVENT END:VCALENDAR
Created attachment 134875 [details] test event 11am created in evolution sorry, reuploading to obscure my gcal URL ;)
Created attachment 134876 [details] test event 11am created in lightning and here's the lightning one again. sorry people, I really didn't mean to add all this clutter, if anyone knows how to delete my obsolete comments I would appreciate it.
Glad to see activity in this bug after long time. :) rob: I've heard attachments or comments can't be deleted.
Google supports accessing calendar via caldav interface and milan is working on that. Once we are sure that all things work fine. we will prune the backend alone and allow google to be accessed with caldav. Since the maintainer of google calendar is not going to be working anymore due to his personal reasons, we are thinking to go with this decision. IMHO this not a blocker as it is a bug in a specific backend.
Yes, I have found that this issue does not occur when using caldav, so sounds like a good plan to me.
(In reply to comment #16) > Google supports accessing calendar via caldav interface and milan is working on > that. Once we are sure that all things work fine. we will prune the backend > alone and allow google to be accessed with caldav. That's correct. I test things with a google server (and also some other), and it seems to work fine. Though there are some issues, with which I cannot do much, I believe, thus I filed them to the google's caldav issues. You can see them here: http://code.google.com/p/google-caldav-issues/issues/list?thanks=38&ts=1243936338 They do not have there many filled, so hopefully they'll look at some of them soon (though I doubt it, somehow). But let's see. Anyway, if you want, you can always test evolution CalDAV with Google and report issues here, and I'll try to look at them (preferably CC me on those, as I do not read all new evo bugs).
*** This bug has been marked as a duplicate of bug 544469 ***