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 270631 - Exchange connector crashes, cannot use exchange calender thereafter
Exchange connector crashes, cannot use exchange calender thereafter
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.0.2
Other All
: Normal major
: 2.5
Assigned To: Chenthill P
Ximian Connector QA
Depends on:
Blocks: 327514
 
 
Reported: 2004-12-17 12:18 UTC by Poornima
Modified: 2006-02-13 09:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb traces while it was hagningh for 30 minutes (6.82 KB, text/plain)
2004-12-17 12:36 UTC, Poornima
Details
bug- buddy traces (14.67 KB, text/plain)
2004-12-17 12:37 UTC, Poornima
Details

Description Poornima 2004-12-17 12:18:00 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. Send a recurrence meeting from user1 to user2. Recurrence for 999
2. Login to OWA as 'User1'. 
2. In meeting fill up summary, location, description, uncheck 'All Day Event'.
3. User2 accepted the appointment, u can see in calender the list of
appointment in 'List' view.
4. Delete an appoinment from 'User1's list of appoinment, send notice to user2.
5. User2 will accept the changes, but due to problem in 'List' view cannnot
see the changes.  Now manually delete any 2 appointments from 'Users2'
lists of recurring appointments.  
6.From 'OWA' where you have logged in as 'User1', select those two 
appointments which were deleted from 'User2's list of appointment. Update
summary of both the appointment, then send it.
7.Now in 'User2' evolution mail cleint, click on 'Mail' component. Then
open the first mail and accept the update. Then open the second mail and
accept the update. Exchange connector crashed.
Therafter click on 'Calender' component, then on exchange calender folder,
exchange connector crashes always.    
Actual Results:


Expected Results:


How often does this happen? 
Always

Additional Information:
Comment 1 Poornima 2004-12-17 12:36:16 UTC
Created attachment 44498 [details]
gdb traces while it was hagningh  for 30 minutes
Comment 2 Poornima 2004-12-17 12:37:17 UTC
Created attachment 44499 [details]
bug- buddy traces
Comment 3 christine 2005-02-01 16:40:54 UTC
does this corrupt the calendar in some way that means Connector can no
longer view/use the calendar ever again?  
Comment 4 Poornima 2005-02-02 05:51:05 UTC
yes cannot use calender at all, i had delete that test id from
exchange server and recreate for further testing
Comment 5 christine 2005-02-02 14:41:39 UTC
this is really bad - glad to see no known dupes from customers. this
needs dev investigation and hopefully fixing asap! 
Comment 6 JP Rosevear 2005-03-08 17:59:49 UTC
The categories code in the backtrace is dead in 2.1/2.2.  Poornima,
can you regress this against 2.1/2.2?  Christine, its up to you if you
want this checked out for 2.0.x.
Comment 7 Poornima 2005-03-11 16:15:32 UTC
This bug cannot be regressed till send updates for 'Single instance'
in recurring appointments works.
Comment 8 christine 2005-03-25 01:47:45 UTC
if there is any chance this calendar corruption can happen in the real
world, then this should be fixed in 2.0.x and 2.2.x.  
Comment 9 Sushma Rai 2006-01-11 09:40:31 UTC
This needs to be tested now.
Comment 10 Chenthill P 2006-02-13 09:01:35 UTC
Have committed the fix for this on 2006-01-04.