Created attachment 458233 [details]
File: backtrace

Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=634288

*** Bug 651397 has been marked as a duplicate of this bug. ***

*** Bug 693714 has been marked as a duplicate of this bug. ***

Hello,
can the mantainer of the package push urgency or ask news to upstream?
It has been more than 5 months...
I can post more debugging if necessary or do testing of use cases..

If it may help, I have been using evolution and mapi since more than one month, but I'm experiencing this problem only in the latest few days:
# ll /var/log/messages*
-rw------- 1 root root  303693 Apr  6 09:06 /var/log/messages
-rw------- 1 root root 1024315 Mar 13 14:07 /var/log/messages-20110313
-rw------- 1 root root  705202 Mar 21 10:30 /var/log/messages-20110321
-rw------- 1 root root  919729 Mar 28 09:34 /var/log/messages-20110328
-rw------- 1 root root  907904 Apr  4 11:28 /var/log/messages-20110404

# grep segfault /var/log/messages* | grep evolution
/var/log/messages:Apr  5 13:09:21 ope46 kernel: [14722.384842] evolution[16636]: segfault at 10 ip 0000003d41a77703 sp 00007f047e9d4a10 error 6 in libc-2.13.so[3d41a00000+191000]
/var/log/messages-20110404:Apr  1 12:19:41 ope46 kernel: [12050.937899] evolution[2773]: segfault at 10 ip 0000003d41a761c9 sp 00007fffc5e32570 error 4 in libc-2.13.so[3d41a00000+191000]

My updated packages between 30/03 and 01/04:
Mar 31 01:07:31 Installed: pidgin-2.7.11-1.fc14.x86_64
Mar 31 01:08:26 Installed: libsexy-0.1.11-15.fc13.x86_64
Mar 31 01:08:27 Installed: libntlm-1.2-1.fc13.x86_64
Mar 31 01:08:29 Installed: 1:xchat-2.8.8-6.fc14.x86_64
Mar 31 01:11:05 Installed: xchat-gnome-0.26.1-14.fc14.x86_64
Mar 31 01:13:03 Installed: irssi-0.8.15-3.fc14.x86_64
Apr 01 09:01:49 Updated: cronie-1.4.7-1.fc14.x86_64
Apr 01 09:01:51 Updated: cronie-anacron-1.4.7-1.fc14.x86_64
Apr 01 09:01:55 Updated: 2:qemu-common-0.14.0-6.fc14.x86_64
Apr 01 09:01:57 Updated: 2:qemu-system-x86-0.14.0-6.fc14.x86_64
Apr 01 09:02:00 Updated: qtcurve-gtk2-1.8.5-4.fc14.x86_64
Apr 01 09:02:10 Updated: gnome-pilot-2.32.1-1.fc14.x86_64
Apr 01 09:02:12 Updated: sox-14.3.2-1.fc14.x86_64
Apr 01 09:02:12 Updated: 2:qemu-img-0.14.0-6.fc14.x86_64
Apr 01 09:02:13 Updated: thai-scalable-fonts-common-0.4.15-2.fc14.noarch
Apr 01 09:02:15 Updated: thai-scalable-waree-fonts-0.4.15-2.fc14.noarch
Apr 01 09:02:16 Updated: 2:qemu-kvm-0.14.0-6.fc14.x86_64
Apr 01 09:02:16 Updated: 2:qemu-kvm-tools-0.14.0-6.fc14.x86_64

In terms of environment the main usage difference is that I have 4Gb of ram on my laptop and in the latest days I'm keeping open a Win7 KVM guest that is configured with 1.5Gb of ram.
I don't know if in some way shortage of memory could be of any influence in this bug happening....
When I had the two segfaults events, I went to lunch and after coming back in an hour and a half I found the problem arose...

Hi, this is harder, because it's not clear to me what could happen that it crashes this way. I can think of trying to give a try to valgrind, but evolution is nearly unusable with it, at least for a daily work. Maybe if you could keep it running during a night or in a background, then it will be fine. Please make sure you've installed latest debug-info packages for gtkhtml3, evolution-data-server, evolution, evolution-mapi, openchange and samba4, and then run evolution like this:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt

When/if evolution crashes, then the log.txt file may contain all relevant information for us. Thanks in advance.

*** Bug 701563 has been marked as a duplicate of this bug. ***