Red Hat Bugzilla – Bug 358491
[RHEL5] evolution does not show recurrence of accepted meeting invites
Last modified: 2008-05-21 11:18:59 EDT
Description of problem:
If you accept a meeting invite (ics attachment) in evolution that contains
recurrence, evolution will store the event in the users calendar as expected,
but will not show the recurrening events. evolution writes the ics file
(~/.evolution/calendar/local/system/calendar.ics) with recurrence, but does not
show it in calendar component, for example:
SUMMARY:test / Breakfast meeting
Version-Release number of selected component (if applicable):
send meeting invite with recurrence to evolution user, accept meeting, check
event is stored in users calendar, but only the first occurence shown.
This is misleading both users involved: the sender receives an email stating
accpetance and the receiver does not know about the recurrence.
show event with recurrence
As evolution is heavily user internally at Red Hat, this should be fixed with
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Created attachment 291862 [details]
proposed evo patch
I found out that the event is just the instance, and not the master object of
the event, so it is recurring, but is stored as an exception of the master
object. The problem was with the Evolution, it sent always the event instance,
except when creating new meeting.
This patch will send changes based on the modify mode chosen by user (the
dialog which asks what to modify, all instances or only this instance).
I also moved this upstream, see  for more details.
Hmm, I'm still able to reproduce the problem with the patch applied, although it
took several tries for the event to even show up. Marking this MODIFIED anyway;
I think we can still figure this out before 5.2 ships.
Patch applied to evolution-2.12.3-2.el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.