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 531841 - Google calendar issues
Google calendar issues
Status: RESOLVED DUPLICATE of bug 535745
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-06 21:48 UTC by Jean-Christophe Taboada
Modified: 2008-07-25 06:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Jean-Christophe Taboada 2008-05-06 21:48:53 UTC 
Hi, just been using Evolution for a long time without ANY problem whatsoever, but since I updated my system to 9.04, I got a 2.2 version of Evolution, and have not been able to use correctly the "google" Calendars functionality : I have several different calendars, each with the same username / password, but it looks like each time I got the same data from the google server. Furthermore, if I try to edit/delete one of them, I loose ALL of them... Very puzzling (and frustrating ;-)


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.1 2008-04-15 (Ubuntu)
BugBuddy Version: 2.22.0
Comment 1 André Klapper 2008-05-09 21:30:37 UTC 
no, you upgraded to 8.04, and you run 2.22. :)
Comment 2 Jean-Christophe Taboada 2008-05-10 19:36:29 UTC 
Oups, sorry. You're right. It IS Ubuntu 8.04 and Evolution 2.22. But in any case, I still cannot figure out how I can have several calendars within Evolution.
Comment 3 Suman Manjunath 2008-05-30 15:28:11 UTC 
CC'ing Ebby
Comment 4 Akhil Laddha 2008-06-13 05:24:59 UTC 
Currently evolution supports only default google calendar see bug 535745
Comment 5 Milan Crha 2008-07-25 06:10:55 UTC 
I'll mark this as duplicate of the Akhil's bug, because when I tried with patches from there then it works as expected, thus should be same issue.

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