Bug 588514 - [abrt] crash in evolution-2.28.3-1.fc12: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] crash in evolution-2.28.3-1.fc12: Process /usr/bin/evolution was kille...
Status: CLOSED DUPLICATE of bug 570399
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-05-03 16:41 EDT by Dave Gordon
Modified: 2010-05-25 05:00 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:00:27 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 (30.08 KB, text/plain)
2010-05-03 16:41 EDT, Dave Gordon
no flags Details

  None (edit)
Description Dave Gordon 2010-05-03 16:41:02 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/evolution
comment: There was an update just moments prior to opening Evolution, do not know if that may have helped the crash or not... the update did not appear to affect Evolution or its dependencies.
component: evolution
executable: /usr/bin/evolution
global_uuid: 0a2b0794be73493cf95a16b21dfa0cd9395415e7
package: evolution-2.28.3-1.fc12
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. Opened Evolution, used scroll wheel (up) crash! 
Comment 1 Dave Gordon 2010-05-03 16:41:06 EDT
Created attachment 411122 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:00:27 EDT

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

Sorry for the inconvenience.

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