Bug 619213 - [abrt] crash in evolution-2.30.2-1.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] crash in evolution-2.30.2-1.fc13: raise: Process /usr/bin/evolution wa...
Status: CLOSED DUPLICATE of bug 631671
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-28 17:28 EDT by kinlaso
Modified: 2010-11-09 11:30 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 11:30:47 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 (64.62 KB, text/plain)
2010-07-28 17:28 EDT, kinlaso
no flags Details

  None (edit)
Description kinlaso 2010-07-28 17:28:55 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: I originally did an Evolution restore from Ubuntu.  I did this because I didn't want to set up all my email account information.  I have multiple emails.  Ever since then, it will crash often.  It normally crashes when I enter my passwords for retrieving mail.
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: fa2414e76b350e1a027b9ada9cffc2e1951096c4
package: evolution-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.  I open evolution mail.
2. I put in my password for the imap.
3. Evolution crashes, not everytime, but often.
Comment 1 kinlaso 2010-07-28 17:28:56 EDT
Created attachment 435132 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 11:30:47 EST

*** This bug has been marked as a duplicate of bug 631671 ***
Comment 3 Karel Klíč 2010-11-09 11:30:47 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 #631671.

Sorry for the inconvenience.

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