Bug 589468 - [abrt] crash in evolution-2.28.3-1.fc12: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in evolution-2.28.3-1.fc12: Process /usr/bin/evolution was kille...
Status: CLOSED DUPLICATE of bug 556939
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c81eb7ade8ad18421bbcb114c1d...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-06 08:55 UTC by Dundee
Modified: 2010-05-25 10:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 10:03:04 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 (65.69 KB, text/plain)
2010-05-06 08:55 UTC, Dundee 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Dundee 2010-05-06 08:55:11 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
global_uuid: c81eb7ade8ad18421bbcb114c1da0abac55e7146
kernel: 2.6.32.11-99.fc12.x86_64
package: evolution-2.28.3-1.fc12
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Click on button to compose new mail
2.
3.
Comment 1 Dundee 2010-05-06 08:55:15 UTC 
Created attachment 411880 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:03:04 UTC 

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

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