Bug 666607

Summary: [abrt] evolution-2.32.1-1.fc14: build_template_menus_recurse: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bill Mauer <IAGolem>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: e.liger, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7210c8b27cdda54e8ac65c7a8d31388fc0ad9639
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-06 11:25:08 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 Bill Mauer 2011-01-01 12:15:10 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
comment: Crashes consistently. Imported from an earlier version (.gz export file). 
component: evolution
crash_function: build_template_menus_recurse
executable: /usr/bin/evolution
kernel: 2.6.35.10-74.fc14.i686
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: 1293883844
uid: 500

How to reproduce
-----
1. Start Evolution Mail
2. Click on any mail folder
3. Crash
Comment 1 Bill Mauer 2011-01-01 12:15:13 UTC 
Created attachment 471323 [details]
File: backtrace
Comment 2 Milan Crha 2011-01-06 11:25:08 UTC 
Thanks for a bug report. There is filled the same 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=633854
Comment 3 Milan Crha 2011-01-06 11:34:42 UTC 
*** Bug 666206 has been marked as a duplicate of this bug. ***