GNOME Bugzilla – Bug 270631
Exchange connector crashes, cannot use exchange calender thereafter
Last modified: 2006-02-13 09:01:35 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:
Created attachment 44498 [details] gdb traces while it was hagningh for 30 minutes
Created attachment 44499 [details] bug- buddy traces
does this corrupt the calendar in some way that means Connector can no longer view/use the calendar ever again?
yes cannot use calender at all, i had delete that test id from exchange server and recreate for further testing
this is really bad - glad to see no known dupes from customers. this needs dev investigation and hopefully fixing asap!
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.
This bug cannot be regressed till send updates for 'Single instance' in recurring appointments works.
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.
This needs to be tested now.
Have committed the fix for this on 2006-01-04.