If you think your authentication failure may be due to CAPTCHA, try using the unlock URL to tell Google you are human.
https://www.google.com/accounts/UnlockCaptcha I have not had a re-occurrence yet, but online docs suggest it will work. The only way to confirm auth failures are indeed CAPTCHA (and not some other issue) is to disable the calendar (to stop the password prompts) and then navigate to the Properties and Retrieve the Calendars. It seems that this invokes the libgdata interface that will report back the CAPTCHA failure. According to the upstream developers the CalDAV interface being used does not properly support the CAPTCHA exception, so this issue will remain until things cutover entirely to the new auth mechs in libgdata or Google updates how the CalDAV interface works. Similar issues happen to iPhone users who integrate Calendars via CalDAV: http://www.google.com/support/forum/p/Calendar/thread?tid=78dc7e4076e4fe26&hl=en Another workaround if the unlockURL does not work may be to hit the CalDAV interface in your browser and see if it gets unlocked there (and capture any undocumented CalDAV failure exception). Server: https://www.google.com/calendar/dav/y...@gmail.com/user/ Note: if you are trying to sync a secondary calendar, use this URL Server: https://www.google.com/calendar/dav/[string of numbers and letters]@group.calendar.google.com/user/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/854232 Title: Google authentication failing due to CAPTCHA To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/854232/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
