Bug 598189

Summary: [abrt] crash in evolution-2.30.1-6.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Greg Ennis <pomec>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:20f47ee86bb5974629761d50c3fcfebe8f503a72
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 15:00:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Greg Ennis 2010-05-31 17:14:52 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 20f47ee86bb5974629761d50c3fcfebe8f503a72
kernel: 2.6.33.4-95.fc13.i686.PAE
package: evolution-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
I performed an upgrade from F12 to F13 using preupgrade-cli.  I had some difficulty at first with not sufficient disk space on /boot. but I followed the directions in the FAQ and was able to do the upgrade without difficulty.  

When I started to use evoloution on the new Fc13 system it has failed about 5 times.  Sometimes the failure is when I am trying to read an e-mail and sometimes as an e-mai is being downloaded from the IMAP server.

How to reproduce
-----
1.Unknown at this time
2.
3.
Comment 1 Greg Ennis 2010-05-31 17:14:54 UTC 
Created attachment 418350 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:00:31 UTC 

*** This bug has been marked as a duplicate of bug 607187 ***
Comment 3 Karel Klíč 2010-11-09 15:00:31 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #607187.

Sorry for the inconvenience.