Bug 703174

Summary: [abrt] evolution-2.32.2-1.fc14: update_or_redraw: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Rafael Soares (Tuelho) <rsoares>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: darren.armstrong, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:9cca0b62b11b3d1115af9880a49390acc38622e2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-10 04:14:07 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 Rafael Soares (Tuelho) 2011-05-09 14:42:37 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 53069 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 159248384 bytes
crash_function: update_or_redraw
executable: /usr/bin/evolution
kernel: 2.6.35.12-90.fc14.i686.PAE
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1304948929
uid: 500

How to reproduce
-----
1. Trying to edit the Cc: field when fowarding email on Evolution
2.
3.
Comment 1 Rafael Soares (Tuelho) 2011-05-09 14:42:42 UTC 
Created attachment 497819 [details]
File: backtrace
Comment 2 Milan Crha 2011-05-10 04:14:07 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=649848
Comment 3 Milan Crha 2013-09-18 09:59:22 UTC 
*** Bug 1009194 has been marked as a duplicate of this bug. ***