Evolution does not sync with Google Calendar

[traist120]

Description: Ubuntu jaunty (development branch)
Release: 9.04
evolution:
  Installed: 2.25.92-0ubuntu1
  Candidate: 2.25.92-0ubuntu2
  Version table:
     2.25.92-0ubuntu2 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
 *** 2.25.92-0ubuntu1 0
        100 /var/lib/dpkg/status

Usually, when I choose to use Google Calendar as a source, it works just fine. But now, I can't use it from CalDev, or from Google Calendar. This also might be error on my part, but usually it works.

[Pedro Villavicencio (pedro)]

Thanks for the report, how are you creating that calendar? may you tell us a few easy steps in order to reproduce the issue? are you using a web calendar or one created in gmail with your username and password?

[traist120 (travist120)]

Bug #33785
Evolution does not sync with Google Calendar

Steps to recreate
• Right Click -> New Calendar
• Type: Google
• Name: Google Calendar
• Checked "Copy calendar contents locally for offline operation"
• Checked "Mark as default calendar"
• Clicked Okay
• Click "Send / Receive"
• ....nothing.
• Right Click Google Calendar -> Properties
• change Name to "<email address hidden>"
• click "send / receive"
• ...nothing.

Now, I don't know if there's something I'm supposed to put in or something like that. But I am only given a few options, and none pertain to a username or password what so ever.

I have also tried the calDav version, and I can't get that to work either.

[mykrob (myk-robinson)]

I use Google Calendar as well, and it works fine in Intrepid. I notice two things missing in Jaunty when selecting Google for your calendar, and these two things are key.. The username and password fields are missing. The "name" field is not the same as username, and since you cannot provide a valid username or password, there is no way for Evolution to connect with Google to fetch the calendar.

[Sebastien Bacher (seb128)]

could somebody having the issue open a bugzilla.gnome.org bug?

[Sebastien Bacher (seb128)]

seems similar to bug #256978