Bug 652394 - [abrt] evolution-2.32.0-2.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.0-2.fc14: Process /usr/bin/evolution was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 805707
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bb27c2cc72fc0f0d650118d7dbf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-11 19:26 UTC by dev
Modified: 2012-03-30 12:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:37:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (60.88 KB, text/plain)
2010-11-11 19:26 UTC, dev 		no flags Details
View All

Description dev 2010-11-11 19:26:25 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289430003
uid: 500
Comment 1 dev 2010-11-11 19:26:28 UTC 
Created attachment 459829 [details]
File: backtrace
Comment 2 Milan Crha 2010-11-12 08:41:31 UTC 
Thanks for a bug report. Is this consistently reproducible, please? I do not know what you did exactly, but it seems to me that you chose a message for viewing. It's possible that this crash is related to some particular mail, thus if you can reproduce this, could you strip private information from the message itself and attach it here for testing purposes, please? Thanks in advance.
Comment 3 abrt-bot 2012-03-30 12:37:55 UTC 
Backtrace analysis found this bug to be similar to bug #805707, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 805707 ***
Note You need to log in before you can comment on or make changes to this bug.