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 599226 - Unable to accept meeting invitation to Google Calendar from evolution
Unable to accept meeting invitation to Google Calendar from evolution
Status: RESOLVED DUPLICATE of bug 588858
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-10-21 18:46 UTC by ircone
Modified: 2009-10-26 18:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description ircone 2009-10-21 18:46:19 UTC
Not sure whether this is an evolution bug or a libgdata bug.  Was testing in Karmic Koala and found this issue.  Was advised that this issue was upstream from Ubuntu so reporting it here.

Steps taken to reproduce issue:
1. Open Evolution
2. Set up a Google calendar in Evolution (Under calendar, select "new calendar" type of "Google" and enter credentials)
3. Receive a meeting invitation in Evolution.
4. In the invitation, select your Google calendar and hit "Accept"
5. Receive the error "Unable to send item to calendar '<Google calendar name>'. Authentication failed."

Expected behavior: To accept the meeting request and publish the event to the Google calendar

Actual behavior: Rejected due to "failed authentication."

I can create a Google calendar event from Evolution outside the context of accepting a meeting invite, so the authentication should work for accepting an invite as well.
Comment 1 Philip Withnall 2009-10-23 10:26:29 UTC
Evolution currently uses its own internal copy of (a different) libgdata. This is not a libgdata bug.
Comment 2 Milan Crha 2009-10-26 18:32:10 UTC
It depends on the version of evolution. Based on the error message I guess it's 2.28, thus google through CalDAV, thus issue in Google itself, as is stated in bug #588858

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