Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 454527

Summary: Caldav and recucurring Appointments
Product: [Fedora] Fedora Reporter: Ronald Kuetemeier <bugzilla>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 9CC: mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-15 10:11:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ronald Kuetemeier 2008-07-08 21:34:52 UTC
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:


Comment 1 Milan Crha 2008-07-14 14:17:07 UTC
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.

Comment 2 Ronald Kuetemeier 2008-07-14 14:33:43 UTC
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.

Comment 3 Milan Crha 2008-07-15 10:11:58 UTC
I can reproduce this bug. I will move it upstream, add yourself to the upstream
bug [1] for further information. Thanks for reporting this.