Incorrect syncing of google calender events

Bug #290368 reported by Andrew Fenn
4
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Medium
evolution (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Some would call this a feature, for me it's a bug.

Two computers one is set to one time zone, perhaps +7 GMT (computer 1) the other is +0 GMT (computer 2).

If computer 1 syncs with the google calender first, when computer 2 syncs the times are wrong. On my +7 GMT computer the event time is correct 3:15pm however on computer 2 the time of the event is marked as 8:15 pm.

This is because in my Google calendar settings the time zone is set to +7 GMT hence why computer 2 is wrong.

This is correct functionality, however I also need an option so that whatever time zone the computer is set to it always displays the time given in the time zone it is set so both computer 1 and 2 would be set to 3:15 pm.

Revision history for this message
Ian Weisser (ian-weisser) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* What application(s) are you using?
* What specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Revision history for this message
Andrew Fenn (andrewfenn) wrote :

The steps are described above but the application is of course evolution calendar.

This effects any and all distributions of Ubuntu.

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Changed in evolution:
status: New → Triaged
Changed in evolution:
status: Unknown → New
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Upstream bug has been marked as duplicate of bug https://bugzilla.gnome.org/show_bug.cgi?id=544469

Changed in evolution:
status: New → Unknown
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Comment from upstream:
>>>
It displays time properly in 2.27.91.
<<<
Since Ubuntu 9.10 already shipps with 2.27.92 I am closing this bug. Thanks for reporting.

Changed in evolution (Ubuntu):
status: Triaged → Fix Released
Changed in evolution:
status: Unknown → Fix Released
Changed in evolution:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.