Bug 676391

Summary: [abrt] evolution-2.32.1-1.fc14: imapx_command_select_done: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: John F <johnhford>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: lucilanga, mbarnes, mcrha, py
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:4bdf21c226ee71aeca82b908a2fbedf86ab31ede
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-10 09:46:00 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 John F 2011-02-09 17:48:55 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: imapx_command_select_done
executable: /usr/bin/evolution
kernel: 2.6.35.10-74.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: 1297272796
uid: 500

How to reproduce
-----
I was checking my email in evolution.  I clicked on a message and only saw a 'loading message' display which lasted for quite some time.
Comment 1 John F 2011-02-09 17:48:57 UTC 
Created attachment 477873 [details]
File: backtrace
Comment 2 Milan Crha 2011-02-10 09:46:00 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=639717
Comment 3 Milan Crha 2011-08-04 05:50:06 UTC 
*** Bug 727940 has been marked as a duplicate of this bug. ***