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 710785 - Recurring events repeat eternally despite occurence limit
Recurring events repeat eternally despite occurence limit
Status: RESOLVED DUPLICATE of bug 710683
Product: evolution
Classification: Applications
Component: Calendar
3.10.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-10-24 10:01 UTC by Tobias Getzner
Modified: 2013-10-24 19:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tobias Getzner 2013-10-24 10:01:49 UTC 
I am currently on Evolution 3.10.1.

When specifying a recurring event, the event will recur eternally, despite setting a finite maximum number of occurences. Eternal recurrence does not occur when setting a maximum date.

I have been noticing this when all recurring events I ever specified suddenly started reappearing and completely cluttering my schedule, so that I had to manually delete all past recurring events.
Comment 1 Matthew Barnes 2013-10-24 15:45:50 UTC 
What's your libical version?

I thought I read something about libical 1.0 having some issue with recurrences, but haven't been following that closely.
Comment 2 Tobias Getzner 2013-10-24 19:27:40 UTC 
This is on libical 1.0. I experimentally downgraded to 0.48 and it seems the issue doesn't crop up then. Although it's a bit puzzling, since I'm on libical 1.0 since May, and the recurring events which suddenly flooded the schedule must have already been created with 1.0.
Comment 3 Matthew Barnes 2013-10-24 19:45:29 UTC 
There seems to have been some recent bugfix/change to libical 1.0 which had this side-effect.  I'm still coming up to speed on what happened, but this is covered in bug 710683.

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