Bug 238497

Summary: Evo crashes while sorting message list by "to" column
Product: [Fedora] Fedora Reporter: Peter Jones <pjones>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bkahn, jwboyer, sangu.fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: evolution-2.10.1-10.fc7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-01 15:58:50 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:
Bug Depends On:    
Bug Blocks: 150225    
Attachments:
Description Flags
Patch that fixes the crash (correctly, I think) none

Description Peter Jones 2007-04-30 21:18:36 UTC 
Description of problem:  I clicked the "To" column header to sort by recipients
in my Sent mail folder, and evo crashed.


Version-Release number of selected component (if applicable): 2.10.1-4.1 (but it
appears this crash was present in 2.9 as well).


How reproducible: Not sure; it only happens when it treats the field as
"normalized", but I don't know when that is.

Patch attached.
Comment 1 Peter Jones 2007-04-30 21:18:36 UTC 
Created attachment 153827 [details]
Patch that fixes the crash (correctly, I think)
Comment 2 Matthew Barnes 2007-05-01 15:58:50 UTC 
Confirmed that the patch fixes the crash.  Thanks Peter!

This turned out to be a bug in a patch I submitted for [1].
It's only in Rawhide, not upstream.

Fixed in evolution-2.10.1-10.fc7.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=363695
Comment 3 Matthew Barnes 2007-05-01 16:08:51 UTC 
*** Bug 233613 has been marked as a duplicate of this bug. ***
Comment 4 Matthew Barnes 2007-05-01 16:12:44 UTC 
*** Bug 234675 has been marked as a duplicate of this bug. ***
Comment 5 Matthew Barnes 2007-05-01 16:28:00 UTC 
*** Bug 220371 has been marked as a duplicate of this bug. ***