Re: [Evolution] MAPI/Calendar: Message did not receive a reply (timeout by message bus)

On Mon, 2010-06-28 at 01:46 -0700, Andre Pietsch wrote:
Thread 1 (Thread 0x7ffff7fc07a0 (LWP 24685)):
#0  0x00007ffff43c8d02 in memcpy () from /lib/
#1  0x00007ffff159226e in ndr_push_bytes () from /usr/lib/
#2  0x00007ffff1592334 in ndr_push_array_uint8 () from
#3  0x00007ffff19bb08d in ndr_push_SBinary_short () from
#4  0x00007ffff19f755e in ndr_push_mapi_SPropValue_CTR () from
#5  0x00007ffff1a07a94 in ndr_push_mapi_SPropValue () from
#6  0x00007ffff1a08ee8 in ndr_push_mapi_SPropValue_array () from
#7  0x00007ffff1a0b720 in ?? () from /usr/lib/
#8  0x00007ffff1a0e9c8 in ndr_push_EcDoRpc_MAPI_REQ_UNION () from
#9  0x00007ffff1a0eeb7 in ndr_push_EcDoRpc_MAPI_REQ () from
#10 0x00007ffff19b0853 in ndr_push_mapi_request () from
#11 0x00007ffff19b0998 in ndr_push_EcDoRpc () from /usr/lib/
#12 0x00007ffff109de23 in dcerpc_ndr_request_send () from
#13 0x00007ffff109e4d4 in dcerpc_ndr_request () from /usr/lib/
#14 0x00007ffff1a21572 in dcerpc_EcDoRpc () from /usr/lib/
#15 0x00007ffff19aa0ae in emsmdb_transaction () from /usr/lib/
#16 0x00007ffff1993514 in SetProps () from /usr/lib/
#17 0x00007ffff28854c6 in exchange_mapi_modify_item (olFolder=<value
optimised out>, fid=17211068925949771778, mid=<value optimised out>, 
    build_name_id=0x7ffff288cb70 <exchange_mapi_cal_util_build_name_id>,
ni_data=<value optimised out>, build_props=0x7ffff288ab00
    p_data=0x7fffffffd990, recipients=0x0, attachments=0x0,
generic_streams=0x0, options=32) at exchange-mapi-connection.c:2437
#18 0x00007ffff2aa2420 in e_cal_backend_mapi_modify_object (backend=<value
optimised out>, cal=<value optimised out>, calobj=<value optimised out>,
mod=<value optimised out>, 
    old_object=0x7fffffffdb28, new_object=0x7fffffffdb20) at
#19 0x00007ffff7bc9250 in e_cal_backend_sync_modify_object
Does that help?

seems like some issue in openchange. Feel free to file this under
evolution-mpai product in and then it'll be
tracked down to openchange or from where the issue comes. Though it
would be also good to try with openchange svn trunk, because they did
there quite many changes since 0.9, and the 0.10 release is hopefully
near. (Try to convince jacob to include latest openchange svn in his

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]