Bug 466180

Summary: evolution default sorting broken
Product: [Fedora] Fedora Reporter: Dave Maley <dmaley>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-10 12:46:24 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
screenshot #1
none
screenshot #2
none
screenshot #3 none

Description Dave Maley 2008-10-08 21:43:04 UTC 
Description of problem:
evo seems to want to push unread messages to the top, moving read messages below unread messages.


Version-Release number of selected component (if applicable):
evolution-2.24.0-2.fc10.x86_64


How reproducible:
every time


Steps to Reproduce:
1. goto folder w/ unread messages
2. select 1st unread message
3. goto different folder and back again
  
Actual results:
read message will now appear at bottom, below all unread messages


Expected results:
sorting doesn't change


Additional info:
* leave as default sort (ie. don't click any column headers)

I've also seen some strange sorting behavior in folders w/ mailing list archives which seems likely related.

I'll attach 3 screenshots:
- ss1.png == all unread
- ss2.png == 1st message read, others left unread
- ss3.png == messages re-ordered
***reproduction step #3 was performed between ss2.png and ss3.png***
Comment 1 Dave Maley 2008-10-08 21:44:10 UTC 
Created attachment 319806 [details]
screenshot #1
Comment 2 Dave Maley 2008-10-08 21:44:32 UTC 
Created attachment 319807 [details]
screenshot #2
Comment 3 Dave Maley 2008-10-08 21:44:58 UTC 
Created attachment 319808 [details]
screenshot #3
Comment 4 Matthew Barnes 2008-10-10 12:46:24 UTC 

*** This bug has been marked as a duplicate of bug 466431 ***