GNOME Bugzilla – Bug 595810
evolution crashed while doing initial message fetching
Last modified: 2010-01-14 21:23:51 UTC
Evolution 2.29.1 + evolution-mapi 0.29.1 I created a fresh account, in preferences i enabled 'apply filters to new message' option. Evolution crashed in the middle of message fetching. exchange-mapi-connection.c:1342: Entering exchange_mapi_connection_fetch_item: folder-id 0853BD1E00000001 message-id 4858F8EA38000001libexchangemapi-Message: exchange-mapi-connection.c:1344: exchange_mapi_connection_fetch_item: lock(connect_lock) exchange-mapi-connection.c:616: Entering exchange_mapi_util_get_attachments exchange-mapi-connection.c:709: Leaving exchange_mapi_util_get_attachments exchange-mapi-connection.c:805: Entering exchange_mapi_util_get_recipients exchange-mapi-connection.c:842: Leaving exchange_mapi_util_get_recipients exchange-mapi-connection.c:272: Entering exchange_mapi_util_read_body_stream exchange-mapi-connection.c:390: Leaving exchange_mapi_util_read_body_stream libexchangemapi-Message: exchange-mapi-connection.c:1486: exchange_mapi_connection_fetch_item: unlock(connect_lock) ()>, exchange-mapi-connection.c:1488: Leaving exchange_mapi_connection_fetch_item Invalid header line: ' ([Server IP]) with mapi; Thu, 30 Jul 2009 11:40:21 +0'30 Invalid header line: '' exchange-mapi-connection.c:1342: Entering exchange_mapi_connection_fetch_item: folder-id 0853BD1E00000001 message-id 4758F8EA38000001libexchangemapi-Message: exchange-mapi-connection.c:1344: exchange_mapi_connection_fetch_item: lock(connect_lock) exchange-mapi-connection.c:616: Entering exchange_mapi_util_get_attachments exchange-mapi-connection.c:182: Entering exchange_mapi_util_read_generic_stream Attempt to read stream for proptag 0x0E270102 Attempt succeeded for proptag 0x0E270102 (after name conversion) exchange-mapi-connection.c:250: Leaving exchange_mapi_util_read_generic_stream exchange-mapi-connection.c:182: Entering exchange_mapi_util_read_generic_stream Attempt to read stream for proptag 0x0FF90102 Attempt succeeded for proptag 0x0FF90102 (after name conversion) exchange-mapi-connection.c:250: Leaving exchange_mapi_util_read_generic_stream exchange-mapi-connection.c:709: Leaving exchange_mapi_util_get_attachments exchange-mapi-connection.c:805: Entering exchange_mapi_util_get_recipients (evolution:8401): libexchangemapi-WARNING **: exchange-mapi-connection.c:828: exchange_mapi_util_get_recipients() - object has a recipient without a PR_SMTP_ADDRESS PR_RECIPIENTS_FLAGS: 1 PR_SUPPLEMENTARY_INFO_UNICODE: < #5.1.3 smtp;550 5.1.3 STOREDRV.Submit; invalid recipient address> PR_NDR_DIAG_CODE: 32 PR_NDR_REASON_CODE: 0 PR_NDR_STATUS_CODE: 513 PR_REPORT_TEXT_UNICODE: The format of the e-mail address is incorrect. Check the address, look up the recipient in the Address Book, or contact the recipient directly to find out the correct address. PR_REPORT_TIME: Tue 28 Jul 2009 12:16:41 PM IST IST PR_RECIPIENT_TYPE: 1 PR_INTERNET_CPID: 1200 (evolution:8401): libexchangemapi-WARNING **: exchange-mapi-connection.c:828: exchange_mapi_util_get_recipients() - object has a recipient without a PR_SMTP_ADDRESS PR_RECIPIENTS_FLAGS: 1 PR_SUPPLEMENTARY_INFO_UNICODE: < #5.1.3 smtp;550 5.1.3 STOREDRV.Submit; invalid recipient address> PR_NDR_DIAG_CODE: 32 PR_NDR_REASON_CODE: 0 PR_NDR_STATUS_CODE: 513 PR_REPORT_TEXT_UNICODE: The format of the e-mail address is incorrect. Check the address, look up the recipient in the Address Book, or contact the recipient directly to find out the correct address. PR_REPORT_TIME: Tue 28 Jul 2009 12:16:41 PM IST IST PR_RECIPIENT_TYPE: 1 PR_INTERNET_CPID: 1200 exchange-mapi-connection.c:842: Leaving exchange_mapi_util_get_recipients exchange-mapi-connection.c:272: Entering exchange_mapi_util_read_body_stream exchange-mapi-connection.c:182: 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:250: Leaving exchange_mapi_util_read_generic_stream exchange-mapi-connection.c:390: Leaving exchange_mapi_util_read_body_stream exchange-mapi-connection.c:182: 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:250: Leaving exchange_mapi_util_read_generic_stream libexchangemapi-Message: exchange-mapi-connection.c:1486: exchange_mapi_connection_fetch_item: unlock(connect_lock) ;() exchange-mapi-connection.c:1488: Leaving exchange_mapi_connection_fetch_item Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xaa1feb90 (LWP 8445)] 0xb76067b4 in camel_header_raw_append (list=0xaa1fdd44, name=0xaa1fdcd0 "MIME-Version", value=0xa1df06ce "1.0\r", offset=-1) at camel-mime-utils.c:4304 4304 while (l->next) { (gdb) t a a bt
+ Trace 217730
Thread 37 (Thread 0xaa1feb90 (LWP 8445))
(gdb)
I've got the exact same problem running on amd64 bits but with 2.6.31-11 kernel. There is also an Ubuntu bug at https://bugs.launchpad.net/ubuntu/+source/evolution-mapi/+bug/435881.
I see this bug is set as "Status: UNCONFIRMED". I can confirm this bug and will happily provide screenshots and/or videos.
*** Bug 597777 has been marked as a duplicate of this bug. ***
*** Bug 597940 has been marked as a duplicate of this bug. ***
*** Bug 598312 has been marked as a duplicate of this bug. ***
Created attachment 148167 [details] threaded stacktrace hitting the same error as original reporter, but for me it occurs during opening of an email
Forgot tot mention: I'm on Karmic's evolution 2.28.1 w/ evolution-mapi 0.28.0. I hit the error when selecting a random mail from my inbox to read.
I'm starting to feel we are doomed to live without exchange calendar access from linux (as MS wants it to be). It's so quiet here...
As mentioned in a comment on the Launchpad entry about this bug, a fix is available in a PPA. I haven't got time to check just which code patches this problem, but apparently it *is* fixed upstream. Comment on Launchpad is here: https://bugs.launchpad.net/ubuntu/+source/evolution-mapi/+bug/435881/comments/7 PPA with fix on Launchpad is here: https://launchpad.net/~kbuel/+archive/ppa
(In reply to comment #9) > As mentioned in a comment on the Launchpad entry about this bug, a fix is > available in a PPA. I haven't got time to check just which code patches this > problem, but apparently it *is* fixed upstream. > > Comment on Launchpad is here: > https://bugs.launchpad.net/ubuntu/+source/evolution-mapi/+bug/435881/comments/7 > PPA with fix on Launchpad is here: https://launchpad.net/~kbuel/+archive/ppa I don't see any patch on launchpad and user himself mentioned there as temporary fix.
OK, that PPA fixed it for me, Evolution stays running. Then just waiting for more: Missing content (character set problems), addressbook now working, unable to sent messages. Those, to my understanding are reported. Then, evolution shows 2 calendars in exchange for me.
This had been fixed within bug #595355, thus I'm marking it as a duplicate. The patch from that bug had been committed two days later and is part of 0.28.1 official stable release of evolution-mapi. *** This bug has been marked as a duplicate of bug 595355 ***
*** Bug 606991 has been marked as a duplicate of this bug. ***