Bug 683439

Summary: [abrt] evolution-2.91.90-1.fc16: et_get_n_children: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Aaron Sowry <aaron>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:62a14e3120c8ab12101b92bb6a7b733edda32503
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-10 07:20:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Aaron Sowry 2011-03-09 12:24:30 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 25400 bytes
cmdline: evolution
comment: Seems to be 100% reproducable.
component: evolution
Attached file: coredump, 45862912 bytes
crash_function: et_get_n_children
executable: /usr/bin/evolution
kernel: 2.6.38-0.rc7.git2.3.fc16.x86_64
package: evolution-2.91.90-1.fc16
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 16 (Rawhide)
time: 1299673241
uid: 500

How to reproduce
-----
1. Open the Evolution calendar, either via the clock in Gnome Shell or from Evolution itself
2. Evolution crashes almost immediately
3.
Comment 1 Aaron Sowry 2011-03-09 12:24:35 UTC 
Created attachment 483188 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-10 07:20:02 UTC 
Thanks for a bug report. This is crashing in a accessibility (a11y) code of evolution. I guess if you disable it, then the may go away. There is filled a bug about this already, thus I'm marking this one as a duplicate.

*** This bug has been marked as a duplicate of bug 656221 ***