GNOME Bugzilla – Bug 596929
local alarms don't work for google-synced calendar
Last modified: 2017-08-30 13:00:13 UTC
An early version of this bug was originally reported on: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/377246 It was suggested that this be reported upstream here, and the situation has gotten a little more specific: Add a Google Calendar by any method (google, web, or CalDAV, though I find that CalDAV works the best overall, see https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/183846). Create an event on this calendar either via google's web interface or evolution itself. In either case you can set alarms, and the alarm settings appear to sync correctly in either direction. However, the alarm never actually goes off in Evolution or the Gnome desktop, etc. By contrast, if I create an event on a local calendar ("On This Computer") the alarms I set go off as expected (in the upper right of the screen, same place it notifies about new messages) Google itself triggers alarms if I happen to have google open in a browser window. And maybe that's the rationale for disabling local alarms? But I don't _always_ have the google calendar open (that's why I sync it to evolution). And no local alarms = missed appointments. Ubuntu 9.04 Evolution 2.26.1
libgdata (the library Evolution uses and which provides access to Google services) has seen a lot of development and fixes in the last three years. Is this still a problem in Evolution 3.4.2 or 3.2.3?
(In reply to comment #1) > libgdata (the library Evolution uses and which provides access to Google > services) has seen a lot of development and fixes in the last three years. Yeah but we're not using libgdata for Google Calendars. Might be time to reevaluate that though, since Google gives CalDAV no love.
One might verify that the calendar is checked for reminders in Edit->Preferences->Calendar and Tasks->Reminders tab, which is a prerequisite to receive calendar reminders/alarms. There used to be various issues in the evolution-alarm-notify, where some of them got fixed even recently, for 3.26. I'm closing this in favour of it.