GNOME Bugzilla – Bug 770198
Do not override UTC time with a DTSTART zone in e-cal-recur
Last modified: 2018-11-13 19:56:55 UTC
As of the latest release of Evolution I can delete all the appointments in a recurring series of appointments, but, I can't delete just a single appointment in the series. If I try 'make this movable' it creates a new one but the old one doesn't disappear, and still can't be deleted.
Thanks for a bug report. I tried to reproduce this in the current development version with an On This Computer/Personal calendar and I can reproduce it there, the "Delete This Occurrence" makes the UI flash, but the event is still shown in the UI. The reason is that the event has added an exception date, but this is not properly paired with the existing event occurrence. It's due to a bug in the code, which overrides UTC time with the DTSTART zone, which breaks the time comparison. That means that he occurrence is removed, only the UI part shows it incorrectly. I fixed it with the below change. Created commit 5c7579d in eds master (3.21.91+)
Thanks for the quick fix, but, will there be an Evolution update that fixes this, or should I copy the code into my calendar/libecal/e-cal-recur.c, or... ?
The change is in the evolution-data-server, not in the evolution. It will be released within the 3.21.91 development version (and the next 3.22.0 stable release). The older stable branches are effectively dead for the upstream, but any distribution can take the patch and apply it on their own. The evolution will work properly without any change, the update of the evolution-data-server is enough to make it work.
Any idea when version 3.22.0 stable will be released? Evolution isn't usable for me as it currently is.
The core evolution products follow GNOME release schedule. The 3.22.0 had been released yesterday. How does this question qualify as a good reason to reopen the bug report? I miss that.
After v 3.22 was released the Evolution calendar again worked properly, but a month ago Evolution calendar v 3.28 started doing the same thing again. I can't delete just one instance of a recurring appointment; it still appears. But deleting all of the occurrences still works as expected.
Could you open a new bug with detailed steps, please? We are two years further, many things changed meanwhile. Having some data will be also good to have, not talking that the current stable is 3.30.2, not 3.28.x. I tried the "steps" from above in 3.30.2 (as mentioned in comment #1) and "delete this occurrence" works properly here. That's why I'd appreciate also a test event or some more details.