Bug 585461 - [abrt] crash in evolution-2.30.0-3.fc13: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] crash in evolution-2.30.0-3.fc13: Process /usr/bin/evolution was kille...
Status: CLOSED DUPLICATE of bug 574774
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-04-24 03:28 EDT by André Auzi
Modified: 2010-05-25 05:54 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-25 05:54:11 EDT
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 (28.59 KB, text/plain)
2010-04-24 03:28 EDT, André Auzi
no flags Details

  None (edit)
Description André Auzi 2010-04-24 03:28:46 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
global_uuid: 490b1794ecc14f103ba70682f9d5f8fcdbc05ed5
package: evolution-2.30.0-3.fc13
rating: 3
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: N/A

I've just started evolution, removed a couple of non signifiant cron-report mails and iconfied it.
The background process of retreiving the IMAP folders for modified mails was still running.
Comment 1 André Auzi 2010-04-24 03:28:48 EDT
Created attachment 408784 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:54:11 EDT

*** This bug has been marked as a duplicate of bug 574774 ***
Comment 3 Karel Klíč 2010-05-25 05:54:11 EDT
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 #574774.

Sorry for the inconvenience.

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