Bug 623449 - [abrt] crash in evolution-2.30.2-4.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] crash in evolution-2.30.2-4.fc13: raise: Process /usr/bin/evolution wa...
Status: CLOSED DUPLICATE of bug 607187
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-11 15:52 EDT by Jeff Kirsher
Modified: 2010-11-09 10:02 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 10:02:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (56.66 KB, text/plain)
2010-08-11 15:52 EDT, Jeff Kirsher
no flags Details

  None (edit)
Description Jeff Kirsher 2010-08-11 15:52:49 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
comment: I added the "Flag for Follow Up" column to the inbox message window, and Evolution crashed.  Since then, I am not able to open Evolution at all.  It continues to crash upon opening, and does not give me enough time to do anything.
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 63aae33944cd5c4ab6731898b30d8506c724e26c
package: evolution-2.30.2-4.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1. Add the "Flag for Follow up" in the Inbox Display
Comment 1 Jeff Kirsher 2010-08-11 15:52:53 EDT
Created attachment 438277 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 10:02:53 EST

*** This bug has been marked as a duplicate of bug 607187 ***
Comment 3 Karel Klíč 2010-11-09 10:02:53 EST
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.

Note You need to log in before you can comment on or make changes to this bug.