Bug 588199 - [abrt] crash in evolution-2.30.1-2.fc13: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-2.fc13: Process /usr/bin/evolution was kille...
Status: CLOSED DUPLICATE of bug 540533
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b599d99b02fbbfb95f31cfad02c...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-03 06:17 UTC by Milan
Modified: 2010-05-25 09:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 09:54:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (44.28 KB, text/plain)
2010-05-03 06:17 UTC, Milan 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Milan 2010-05-03 06:17:41 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
global_uuid: b599d99b02fbbfb95f31cfad02c9c8dac7c4f5c5
kernel: 2.6.33.2-57.fc13.i686.PAE
package: evolution-2.30.1-2.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. While I was typing e-mail...
2.
3.
Comment 1 Milan 2010-05-03 06:17:43 UTC 
Created attachment 410903 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:54:59 UTC 

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

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