Bug 586496 - [abrt] crash in evolution-2.28.3-1.fc12: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.28.3-1.fc12: Process /usr/bin/evolution was kille...
Status: CLOSED DUPLICATE of bug 573846
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:a5a2e6ef22b27175e6a94457a70...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-27 18:02 UTC by brizly vaan van Ulciputz
Modified: 2010-05-25 08:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-25 08:22:50 UTC
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 (84.44 KB, text/plain)
2010-04-27 18:02 UTC, brizly vaan van Ulciputz
no flags Details

Description brizly vaan van Ulciputz 2010-04-27 18:02:08 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
global_uuid: a5a2e6ef22b27175e6a94457a70ba267e008d764
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
not sure how to reproduce it, evolution was open and i just wanted to read an e-mail that arrived in the past 15min. the e-mail already was open, say, 10sec, when evolution crashed.

Comment 1 brizly vaan van Ulciputz 2010-04-27 18:02:11 UTC
Created attachment 409539 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:22:50 UTC

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

Comment 3 Karel Klíč 2010-05-25 08:22:50 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 #573846.

Sorry for the inconvenience.

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