After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 558398 - Evolution Google Syncronization Calendar fails
Evolution Google Syncronization Calendar fails
Status: RESOLVED DUPLICATE of bug 541432
Product: evolution
Classification: Applications
Component: Calendar
2.24.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[google]
Depends on:
Blocks:
 
 
Reported: 2008-10-29 14:01 UTC by Francisco Urbano García
Modified: 2009-01-09 04:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Francisco Urbano García 2008-10-29 14:01:02 UTC 
Please describe the problem:
When updating the date on Evolution on a Google Calendar, Google gets properly updated but Evolution rolls back to the old date if rebooted.

Sync also fails when a Recurrence is set. If set on Evolution only the first day appears on Google and if set on Google 

Steps to reproduce:
1. Create appointment on Evolution (google) Calendar
2. Update old_time with new_time
3. reboot Evolution


Actual results:
old_time appears on the updated appointment

Expected results:
new_time appears on the updated appointment

Does this happen every time?
yes

Other information:
Comment 1 Pavel Lisý 2008-12-17 10:40:54 UTC 
I can confirm (even extend) this bug. 

Sync fails at all when I edit gcal on google.com site. 

I can see only appointments which I've made from evolution. 

And something for refresh calendar (button or menu) is hardly missing. Even
https://www.google.com/calendar web application have it now.
Comment 2 Akhil Laddha 2009-01-09 04:42:00 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 541432 ***