Bug 580628 - [abrt] crash in evolution-2.30.0-1.fc13: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.0-1.fc13: Process /usr/bin/evolution was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 557720
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d84d72ca0adc9f435626c670920...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-08 16:30 UTC by James Laska
Modified: 2013-09-02 06:47 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-25 10:07:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (57.47 KB, text/plain)
2010-04-08 16:30 UTC, James Laska 		no flags Details
View All

Description James Laska 2010-04-08 16:30:12 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Attempting to respond to an email resulted in a crash
component: evolution
executable: /usr/bin/evolution
global_uuid: d84d72ca0adc9f435626c6709209247986559507
kernel: 2.6.33.1-19.fc13.x86_64
package: evolution-2.30.0-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Click respond to a new email in inbox
2. Write response, and attempt to paste a link into the window

Unclear whether writing the response triggered the failure, or if pasting the link caused it.
Comment 1 James Laska 2010-04-08 16:30:14 UTC 
Created attachment 405353 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:07:36 UTC 

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

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