Red Hat Bugzilla – Bug 454527
Caldav and recucurring Appointments
Last modified: 2008-07-15 06:11:58 EDT
Description of problem:
The cached object uid gets messed up when an recurring appointment is edited.
Therefore the Appointment is not displayed anymore, while alarms still work.
Also the clock shows the Appointment correctly, only Evolution's display is
messed up. The Caldav DB is updated correctly, and reflects the updated item.
Example cached object uid:
What kind of update did you do? Aka which data field did you change? Did you do
that update for all instances or only to one instance? Also, you do not see all
appointments derived from this item or just this one? Why do you think it's
because of messed up UID?
I see this object is only one instance, not a master object (the initial object,
where isn't stored the RECURRENCE-ID), so probably only to one instance? In that
case, the event is divided into two, one master object with an exception and the
detached instance, showed in the date of the change.
Doesn't matter which field you update.
I changed all instances, was playing with it. Also doesn't seem to matter.
All appointments will disappear.
UID seems possible because the calendar shows the appointment, and the alarms
still happen, was just a guess on what is different from everything else.
Don't know anything about the master object, but if I do an SQL search in the
CalDav DB is shows 2 or more objects (mostly identical), but I think they are
not in the cache file there seems to be only one.
I can reproduce this bug. I will move it upstream, add yourself to the upstream
bug  for further information. Thanks for reporting this.