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 715141 - Reminders broken in CalDAV accounts
Reminders broken in CalDAV accounts
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-11-25 08:52 UTC by Tobias Getzner
Modified: 2014-03-27 17:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tobias Getzner 2013-11-25 08:52:00 UTC
When setting reminders for appointments in a CalDAV backend, these reminders are ignored. Reminders for appointments stored locally appear to be functional.

This is on libical 1.0, so the bug might be related to the current bug re. recurring events: https://bugzilla.gnome.org/show_bug.cgi?id=710683
Comment 1 Tobias Getzner 2013-12-16 16:08:18 UTC
Occasionally, some reminders do pop up, albeit several weeks late (so far these all were birthday reminders, so maybe this is a separate issue). Clicking "dismiss" for these reminders then promptly freezes the reminder window ("application not responding").
Comment 2 Milan Crha 2014-03-06 10:27:27 UTC
Thanks for a bug report. I see reminders for my CalDAV calendars without any issue.

Do you have the CalDAV calendar enabled for reminders? (Edit->Preferences->Claendar and Tasks->Reminders tab, the calendar should be checked there).

(In reply to comment #1)
> Occasionally, some reminders do pop up, albeit several weeks late (so far these
> all were birthday reminders, so maybe this is a separate issue).

Right, it might be a different issue.

> Clicking "dismiss" for these reminders then promptly freezes the reminder
> window ("application not responding").

This is an unrelated issue too. Better to not mix many things into one bug report.
Comment 3 Tobias Getzner 2014-03-07 17:00:12 UTC
I can still reproduce this issue on evolution 3.10.4 with a CalDAV backend served by an owncloud instance. Reminders for locally stored events are still functional, while they are ignored for my CalDAV calendars.

(In reply to comment #2)
> Do you have the CalDAV calendar enabled for reminders?
> (Edit->Preferences->Claendar and Tasks->Reminders tab, the calendar should be
> checked there).

All calendars there have reminders enabled. I’ve also tried using “show a reminder before every appointment” instead of setting reminders individually, but this too fails too pop-up any reminders.
Comment 4 Milan Crha 2014-03-10 11:36:12 UTC
I tried to reproduce this with latest Fedora 20 packages (3.10.4-2 for both evolution-data-server and evolution), then I restarted the machine (after the update), and then I tried this:
a) verify the calendar is checked for reminders (just in case, you have it set)
b) on another machine add an appointment with a reminder which should be
   triggered
c) in the 3.10.4-2 machine right-click above the calendar name and
   pick "Refresh", which updates with changes from the server

After few seconds, when the Refresh was done, I received a popup about the alarm.

There can be multiple reasons why it works fine for me but not for you. One of them is that the evolution-alarm-notify process failed to open your ownCloud calendar. Could you close the running evolution-alarm-notify process, and run it from a terminal like this, please?
   $ ALARMS_DEBUG=1 /usr/libexec/evoltuion/3.10/evolution-alarm-notify
which will print many debug information on the console. Search for the name of the ownCloud calendar, it might be shown as part of an "Opening..." debug message.
Comment 5 Tobias Getzner 2014-03-27 12:58:20 UTC
In the mean-time I cleared all Evolution caches, which seems to have resolved this for now. It’s strange because I had this on two different machines. If it should reappear I’ll try producing the desired debug outputs. Thanks!

(Should this be closed WORKSFORME for now?)
Comment 6 Milan Crha 2014-03-27 17:30:33 UTC
Thanks for the update. It'll be good to know what caused the state for you, but as long as you managed to fix it by cleaning-up the local cache and you are fine with this, I'm closing the bug for now.