GNOME Bugzilla – Bug 597777
Evolution Mail and Calendar: Evolution (with evolutio...
Last modified: 2009-10-09 06:52:35 UTC
Evolution (with evolution-mapi) crashes allways when message list is updated from exchgen 2007 and first message is fetched for preview. Distribution: Ubuntu 9.10 (karmic) Gnome Release: 2.28.0 2009-09-21 (Ubuntu) BugBuddy Version: 2.28.0
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Sorry, here is some console output: (evolution:16201): libexchangemapi-WARNING **: exchange-mapi-connection.c:828: exchange_mapi_util_get_recipients() - object has a recipient without a PR_SMTP_ADDRESS PR_DISPLAY_TYPE: 0 PR_OBJECT_TYPE: 6 PR_7BIT_DISPLAY_NAME: xxxxx PR_ORG_ADDR_TYPE: SMTP PR_ORG_EMAIL_ADDR: xxx@xxx.xx PR_RECIPIENT_NUMBER: 1 PR_RECIPIENT_TYPE: 1 PR_INTERNET_CPID: 1252 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) ,,,,,,,,,,,,,, 'xchange-mapi-connection.c:1488: Leaving exchange_mapi_connection_fetch_item Invalid header line: 'Microsoft Mail Internet Headers Version 2.0 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xacc48b70 (LWP 16605)] 0x002e1bc2 in camel_header_raw_append (list=0xacc4818c, name=0xacc48080 "Message-ID", value=0x870946c "<4A865B77.4040200@xxx.xx>\r", offset=-1) at camel-mime-utils.c:4304 4304 camel-mime-utils.c: No such file or directory. in camel-mime-utils.c (gdb) thread apply all bt
+ Trace 218171
Thread 25 (Thread 0xacc48b70 (LWP 16605))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 595810 ***