Bug 909259

Summary:	Accepted meeting gets duplicated
Product:	Red Hat Enterprise Linux 6	Reporter:	Jiri Koten <jkoten>
Component:	evolution-mapi	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4	CC:	mcrha, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	evolution-mapi-0.32.2-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 05:10:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	883017
Bug Blocks:	960054

Description Jiri Koten 2013-02-08 14:19:32 UTC

Description of problem:
When I accept a meeting request, event is properly created in  MAPI Calendar but on next start it gets duplicated, i.e. calendar shows two same meetings in my calendar. 

Tested with MS Exchange 2010 server.

Version-Release number of selected component (if applicable):
evolution-2.28.3-30.el6
evolution-data-server-2.28.3-16.el6
evolution-mapi-0.28.3-11.el6
openchange-1.0-4.el6
samba4-libs-4.0.0-55.el6.rc4

How reproducible:
100%

Steps to Reproduce:
1. From the second account create a meeting request
2. In the first account accept it 
3. Go to Calendar window and check the meeting
4. Restart evo; evolution --force-shutdown
5. Go to Calendar window and check the meeting and check again
  
Actual results:
After accepting, the meeting is properly created in calendar, but on next start it gets duplicated.

Expected results:
There is only one instance of the meeting.

Comment 2 Milan Crha 2013-02-11 10:13:50 UTC

You might see [1], I believe, and it was no fun to fix that properly, as there were few more patches applied in the meantime, in various bug reports, if I recall correctly. The RHEL7 version (currently 3.6.x) does not suffer of this for sure.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=643791

Comment 4 Milan Crha 2013-05-09 10:30:38 UTC

This is not part of 0.32.2, but I make it depend on the bug, thus the backport will be much simpler than with 0.28.3 (I spent half day trying to backport relevant changes between the upstream patch and 0.28.3 on Tuesday, and basically gave up due to complexity of related changes).

Comment 8 Milan Crha 2013-06-11 12:25:51 UTC

The fix for this bug contains upstream fixes:
  https://bugzilla.gnome.org/show_bug.cgi?id=615636
  https://bugzilla.gnome.org/show_bug.cgi?id=629057
  https://bugzilla.gnome.org/show_bug.cgi?id=642951
  https://bugzilla.gnome.org/show_bug.cgi?id=643791
  https://bugzilla.gnome.org/show_bug.cgi?id=648732
  And commit 3b94edcbb87535a3faac9e30277ec214434d7a2c

Comment 12 errata-xmlrpc 2013-11-21 05:10:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1540.html