Description of problem:
An appointment on an Exchange calendar server, deleted with Outlook, still shows
up in the Evolution calendar.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Evolution.
2. Open Outlook 2003
3. In Evolution, click on the âCalendarâ tab.
4. Double-click in any open time frame.
5. In the time frame, enter basic meeting information. Include a reminder.
6. Click on the âMailâ tab to switch out of âCalendarâ view.
7. Go over to Outlook. Click on the âCalendarâ tab.
8. Single-right-click on the newly entered meeting. Scroll down to âX Deleteâ
and delete it.
9. Go back over to Evolution. Click on the âCalendarâ tab. The appointment is
still there. The appointment is also still there after Evolution has been restarted.
Appointment is still there
Appointment has been deleted
Outlook 2003 SP1, and Exchange 2003 SP1 were used on the Windows side.
*** Bug 184108 has been marked as a duplicate of this bug. ***
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Don't close my issues unless you're the developer.
Created attachment 132832 [details]
output of "gconftool-2 --dump /apps/evolution"
I can confirm most of this bug, although I was using OWA instead of Outlook
2003. I cannot confirm the last part of step 9: when I restart Evolution it
seems to update the calendar properly for me. The deleted appointment is gone.
This bug may be much broader than what the problem description states.
Evolution does not seem to pick up on _any_ remote updates to the appointment;
whether deleting it, moving the time, changing the location, etc. Clicking the
"Send / Receive" button seems to have no effect, and I cannot find any other
means to force Evolution to refetch the calendar information.
This issue does not exist in evolution-connector-2.7.4. Evolution sees all of
my updates to the appointment as soon as I make them from OWA. It also sees
when I delete the appointment.
I will scour the upstream bug reports and see if I can locate the bug number(s)
that fixed this. There may be patches that I can backport.
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
Any word on comment 9? Wondering if this can get devel ack.
No, I'm afraid I haven't looked at this further.
Bugzilla isn't granting me permission to devel ack this for some reason, but
I'll put it on my list of bugs to investigate further.
Oh, apparently I do have permission now.
I found a couple of upstream bug reports that may be relevant, but I've not
found any patches. It appears this issue was resolved in the 2.5 development cycle.
I will continue to search.
No update yet, I spent most of the day drilling into bug #199751.
We believe this bug will be fixed in the Evolution 2.8 upgrade option scheduled
for RHEL 4.6. Please feel free to reopen this bug report if the problem still
exists in Evolution 2.8.