Evolution Data Server segfaults when trying to 'accept' an exchange meeting request

Bug #523717 reported by BlueWine
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-mapi (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: evolution-mapi

Ubuntu 9.10
Evolution 2.28.1-0ubuntu2
Evolution-MAPI 0.28.2-0ubuntu1
libmapi0 1:0.8.2+svn1423-1ubuntu1 (if that's even relevant)

Hey. When pressing 'accept' upon receiving an appointment in an exchange inbox, evolution hangs. This is because Evolution-Data-Server segfaults - the following comes out of GDB when this happens:

exchange-mapi-connection.c:1360: Entering exchange_mapi_connection_fetch_item: folder-id 59D2270C0000001B message-id 0000000000000000libexchangemapi-Message: exchange-mapi-connection.c:1362: exchange_mapi_connection_fetch_item: lock(connect_lock)
libexchangemapi-Message: exchange-mapi-connection.c:1504: exchange_mapi_connection_fetch_item: unlock(connect_lock)

exchange-mapi-connection.c:1506: Leaving exchange_mapi_connection_fetch_item
exchange-mapi-connection.c:1866: Entering exchange_mapi_util_resolve_named_prop libexchangemapi-Message: exchange-mapi-connection.c:1868: exchange_mapi_util_resolve_named_prop: lock(connect_lock)
libexchangemapi-Message: exchange-mapi-connection.c:1919: exchange_mapi_util_resolve_named_prop: unlock(connect_lock)

exchange-mapi-connection.c:1921: Leaving exchange_mapi_util_resolve_named_prop
exchange-mapi-connection.c:1105: Entering exchange_mapi_connection_fetch_items: folder-id 59D2270C0000001B libexchangemapi-Message: exchange-mapi-connection.c:1107: exchange_mapi_connection_fetch_items: lock(connect_lock)
libexchangemapi-Message: exchange-mapi-connection.c:1333: exchange_mapi_connection_fetch_items: unlock(connect_lock)

exchange-mapi-connection.c:1335: Leaving exchange_mapi_connection_fetch_items: folder-id 59D2270C0000001B
exchange-mapi-connection.c:2054: Entering exchange_mapi_create_item libexchangemapi-Message: exchange-mapi-connection.c:2056: exchange_mapi_create_item: lock(connect_lock)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6795b70 (LWP 9540)]
0x00fbe037 in memcpy () from /lib/tls/i686/cmov/libc.so.6

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.