GNOME Bugzilla – Bug 669308
Crash in Unsubscribe, stop_notification
Last modified: 2012-02-10 08:44:19 UTC
Evolution 3.3.5 (Exchange 2010) Tried to subscribe to other user's calendar without success then tried to disable mapi account and evolution crashed. Program received signal SIGSEGV, Segmentation fault.
+ Trace 229594
Thread 2 (Thread 0xb5e41b70 (LWP 32037))
Thread 1 (Thread 0xb611c890 (LWP 32033))
(gdb) info registers eax 0x0 0 ecx 0xad33eb70 -1389106320 edx 0x1 1 ebx 0xac543ff4 -1403764748 esp 0xad33df40 0xad33df40 ebp 0xad33dfa8 0xad33dfa8 esi 0x300000f 50331663 edi 0xa3fbfd8 171950040 eip 0xac416abf 0xac416abf <Unsubscribe+63> eflags 0x10206 [ PF IF RF ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 (gdb) list 207 208 notify_ctx = session->notify_ctx; 209 notification = notify_ctx->notifications; 210 211 while (notification) { 212 if (notification->ulConnection == ulConnection) { 213 retval = Release(¬ification->obj_notif); 214 OPENCHANGE_RETVAL_IF(retval, retval, NULL); 215 DLIST_REMOVE(notify_ctx->notifications, notification); 216 break; (gdb)
Is it one of those "with Exchange 2007 server works as expected"? If I recall correctly, there was some issue with notifications reported in one log you gave me some time back. Maybe it's related, maybe it tries to Unsubscribe, even when Subscribe call failed?
Created attachment 206894 [details] [review] proposed oc patch for openchange; Looking around I do not see an issue within evolution-mapi, but I think the issue is with openchange itself, returning success while notification was rejected. Could you try to apply this patch to your openchange, to confirm it fixes the issue for you, before I'll move it to their tracker, please? Note your MAPI mail account should have set "Listen for server changes notification". Also note that closing evolution may not be always sufficient, thus enabling/disabling mail account may do the trick, as it did for you already (at the top of comment #0). You do not need to do anything more, just enable the account which has the "Listen for server notifications" checked already, wait a bit, select its Inbox, and when it's done with the Inbox refresh, then disable the account again. Please watch your console too.
I am not able to reproduce the crash (with both Exchange 2007 server and Exchange 2010 server) after applying patch from comment#2.
Thanks for testing. I moved this to OpenChange as [1]. The workaround is to disable listen for server notifications for your MAPI account. [1] http://tracker.openchange.org/issues/385