Bug 680636

Summary: [abrt] evolution-2.32.1-1.fc14: g_type_check_instance_cast: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kurt Årdal <kurt>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: alejandro.perez.torres, kurt, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:2b81329e34aa258da9c047dcc03db519a8cc7a25
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-28 08:07:29 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 Kurt Årdal 2011-02-26 15:49:04 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 51100 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 166170624 bytes
crash_function: g_type_check_instance_cast
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.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: 1298733561
uid: 500

How to reproduce
-----
1.Select all mail in Inbox
2.Running Message-Filters on all mail (ctrl+y)
3.Evolution crashed
Comment 1 Kurt Årdal 2011-02-26 15:49:07 UTC 
Created attachment 481158 [details]
File: backtrace
Comment 2 Milan Crha 2011-02-28 08:07:29 UTC 
Thanks for a bug report. I moved this upstream as [1]. 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=643452
Comment 3 Milan Crha 2011-06-14 06:13:35 UTC 
*** Bug 713041 has been marked as a duplicate of this bug. ***