Bug 680687

Summary: [abrt] evolution-2.32.1-1.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bruno Martins <bruno>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: geslinux, lucilanga, mbarnes, mcrha, robk
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f8d6284ee07507b3dc05cf59da5c0ee099dc269e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-28 08:10:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Bruno Martins 2011-02-27 00:04:24 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 47892 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 144658432 bytes
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298682379
uid: 500

How to reproduce
-----
1. Nothing...
2.
3.
Comment 1 Bruno Martins 2011-02-27 00:04:27 UTC 
Created attachment 481205 [details]
File: backtrace
Comment 2 Milan Crha 2011-02-28 08:10:38 UTC 
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=596663
Comment 3 Milan Crha 2011-05-31 04:30:26 UTC 
*** Bug 708704 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2012-11-01 11:44:46 UTC 
*** Bug 872034 has been marked as a duplicate of this bug. ***