Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 587308 - [abrt] crash in evolution-2.30.1-1.fc13: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-1.fc13: Process /usr/bin/evolution was kille...
Status: CLOSED DUPLICATE of bug 570827
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:ad2ae7805ed7d1bcfbeb53e9b8b...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-29 15:09 UTC by atdiehm
Modified: 2010-05-25 08:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-25 08:45:21 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (77.84 KB, text/plain)
2010-04-29 15:09 UTC, atdiehm
no flags Details

Description atdiehm 2010-04-29 15:09:24 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Just keeps crashing, haven't found out yet what I think might be common across the crashes...
component: evolution
executable: /usr/bin/evolution
global_uuid: ad2ae7805ed7d1bcfbeb53e9b8b1a4eee6838c15
package: evolution-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 atdiehm 2010-04-29 15:09:25 UTC
Created attachment 410142 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:45:21 UTC

*** This bug has been marked as a duplicate of bug 570827 ***

Comment 3 Karel Klíč 2010-05-25 08:45:21 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 #570827.

Sorry for the inconvenience.

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