abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: evolution comment: see above component: evolution crash_function: raise executable: /usr/bin/evolution kernel: 2.6.33.3-85.fc13.x86_64 package: evolution-2.30.3-1.fc13 rating: 4 reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1284966363 uid: 500 How to reproduce ----- 1.open evolution using evolution-mapi 2.click on send and receive 3.
Created attachment 448376 [details] File: backtrace
Package: evolution-2.30.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open Evolution 2. Allow Evolution to begin downloading new messages and updates Comment ----- I believe there might be some email in my Inbox that's inherently crashing Evolution.
Package: evolution-2.30.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Evolution crashed under my fingers. I don't remember what I was doing.
Package: evolution-2.30.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Evolution just crashed without my interaction.
See also: https://bugzilla.gnome.org/show_bug.cgi?id=630846
Package: evolution-2.30.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Create a MAPI account 2.Wait for a while...
Thanks for a bug report. I'm using Egon's bug to reference this one. As is stated there, the issue is with thread unsafety of libmapi, samba4, talloc and such, but evolution-mapi is using threading very often. It could happen from time to time that some operations overlap, which might not overlap, causing crash like this. evolution-mapi 0.32.0 contains fix which is addressing this issue.