GNOME Bugzilla – Bug 568523
Evolution crashed when synchronizing messages for offline download
Last modified: 2010-06-15 18:01:15 UTC
Steps to reproduce: 1. Enable one exchange folder for offline download 2. Click on the offline/online button at the bottom left corner 3. Click synchronize in the confirmation window Synchronization went fine for some time and then Evo crashed. The folder was having around 685 mails in it. Stack trace: exchange-mapi-connection.c(1244): Entering exchange_mapi_connection_fetch_item: folder-id D5B62E8F2E010001 message-id E6C92E8F2E010001 libexchangemapi-Message: exchange-mapi-connection.c(1246): exchange_mapi_connection_fetch_item: lock(connect_lock) exchange-mapi-connection.c(608): Entering exchange_mapi_util_get_attachments exchange-mapi-connection.c(701): Leaving exchange_mapi_util_get_attachments exchange-mapi-connection.c(717): Entering exchange_mapi_util_get_recipients (evolution.bin:21449): libexchangemapi-WARNING **: exchange-mapi-connection.c:740 exchange_mapi_util_get_recipients() - object has a recipient without a PR_SMTP_ADDRESS PR_OBJECT_TYPE: 6 PR_DISPLAY_TYPE: 0 PR_SEND_INTERNET_ENCODING: 0 PR_RECIPIENT_TYPE: 1 PR_INTERNET_CPID: 1252 exchange-mapi-connection.c(755): Leaving exchange_mapi_util_get_recipients exchange-mapi-connection.c(258): Entering exchange_mapi_util_read_body_stream exchange-mapi-connection.c(168): Entering exchange_mapi_util_read_generic_stream Attempt to read stream for proptag 0x10130102 Attempt succeeded for proptag 0x10130102 (after name conversion) exchange-mapi-connection.c(236): Leaving exchange_mapi_util_read_generic_stream exchange-mapi-connection.c(376): Leaving exchange_mapi_util_read_body_stream Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xaf032b90 (LWP 21552)] cast_mapi_SPropValue (mapi_sprop=0x0, sprop=0x216d8e78) at libmapi/property.c:426 426 libmapi/property.c: No such file or directory. in libmapi/property.c (gdb) t a a bt
+ Trace 211729
Thread 34 (Thread 0xaf032b90 (LWP 21552))
(gdb) Other information:
Might be a dup of bug 566893
should be related to bug 566874
I agree with Akhil, this might be bug #566874, and movement to openchange 0.9 would probably fix it. *** This bug has been marked as a duplicate of bug 566874 ***