After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 235580 - Evo not handling Outlook recurring mtg. changes well
Evo not handling Outlook recurring mtg. changes well
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
1.0.x
Other All
: Normal major
: 2.2.x
Assigned To: Sarfraaz Ahmed
Evolution QA team
evolution[connector]
Depends on:
Blocks: 327514
 
 
Reported: 2002-12-13 18:52 UTC by Tim Lee
Modified: 2006-01-18 13:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fixes the recurrence in exchange backend (16.36 KB, patch)
2005-11-15 10:23 UTC, Sarfraaz Ahmed
none Details | Review
forgot to add the changelog to the earlier patch. (634 bytes, text/plain)
2005-11-28 11:12 UTC, Sarfraaz Ahmed
  Details

Description Tim Lee 2002-12-13 18:52:53 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
Evolution does not handle changes to instances of a recurring sent from
Outlook very well ( ie. organizer of meeting uses Outlook ). See scenarios
below. These are probably related to fixes made for http://bugzilla.ximian.com/show_bug.cgi?id=33875 and releated
to bug#230060


Common initial steps for start of both scenarios
1. Create recurring meeting in Outlook and invite one Evolution account
2. Accept the meeting invitation in Evolution
3. Alter the start and/or end times of on instance of the recurring meeting
in Outlook and send update.
4. Accept update in Evolution. A meetimg with the changed times is created
in Evolution's calendar ( the orginal meeting is removed ).

Scenario one
5. In Outlook change start and/or end times of the same meeting instance
changed in step 3. Send update
6. Accept update in Evolution.
7. A second meeting is created in Evolution's calendar with the new times,
but the meeting created from the first changes ( step 4. ) is not deleted.

Scenario two
5. In Outlook delete the entire recurring meeting ( all instances ) in
Outlook and send cancellation notice.
6. Update Evo's calendar from the cancellation email(s).
7. The changed meeting instance is not deleted.

Additional Information:

Machine Configuration
------------------------------------------------------------------
SunOS physics 5.8 Generic_108528-13 sun4u sparc SUNW,Sun-Blade-100
soup-0.7.10-1.ximian.1
libgtkhtml20-1.0.4-2.ximian.1
libgal19-0.19.3-snap.ximian.200208120551
gtkhtml1.1-1.1.7-1.ximian.2
gal-0.22.0.99-snap.ximian.200212080701
evolution-1.2.1-1.ximian.1
ximian-connector-1.2.1-1.ximian.1
pilot-link-0.9.5-ximian.4
Comment 1 Hans Petter Jansson 2003-03-05 20:00:39 UTC
According to JP's analysis, there is no time to do this for 1.4.
Architectural changes will go into 1.6.
Comment 2 Gerardo Marin 2003-11-30 08:05:49 UTC
Moving all 1.6/2.0 milestones to 1.5.x
Comment 3 Gerardo Marin 2004-01-28 05:43:28 UTC
Retargeting 1.5.3->1.5.4 bug reports. Sorry for the spam.
Comment 4 Brian T. McKee 2005-05-31 16:54:50 UTC
This bug (and possibly related bugs) are stopping Evolution from working for me.
I  work in a large corporate environment. (18,000+ email users) And I'd like to
run linux desktop. However, because my meetings have grown to the point that
they are at (several reoccurring weekly tasks) I can no longer keep Evolution
alive for more than a minute. I tried disabling the calandar, but unchecking the
exchange server, but it still hangs retrieving a mail.

I'm using Evo 2.2.1.1

For more information, please email me: btmckee@micron.com

Brian T. McKee
Comment 5 Chenthill P 2005-08-22 16:48:57 UTC
adding connector keyword.
Comment 6 Sarfraaz Ahmed 2005-11-15 10:23:08 UTC
Created attachment 54777 [details] [review]
Fixes the recurrence in exchange backend
Comment 7 Sarfraaz Ahmed 2005-11-28 11:12:17 UTC
Created attachment 55307 [details]
forgot to add the changelog to the earlier patch.
Comment 8 Sushma Rai 2005-11-28 11:37:38 UTC
Fix committed to both cvs head and gnome-2-10 branch.