Bug 683439 - [abrt] evolution-2.91.90-1.fc16: et_get_n_children: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.91.90-1.fc16: et_get_n_children: Process /usr/bin/evolutio...
Keywords:
Status: CLOSED DUPLICATE of bug 656221
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:62a14e3120c8ab12101b92bb6a7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 12:24 UTC by Aaron Sowry
Modified: 2011-03-10 07:20 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-10 07:20:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (24.80 KB, text/plain)
2011-03-09 12:24 UTC, Aaron Sowry 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.