Bug 16031

Summary: xfce4 and thunar 1.6.6 disordered file order display
Product: Mageia Reporter: Tony Blackwell <tablackwell>
Component: Release (media or process)Assignee: Jani Välimaa <jani.valimaa>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: sysadmin-bugs
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: screenshot of file order
Files/folders sorted by name

Description Tony Blackwell 2015-05-24 10:13:54 CEST
Description of problem:
M5 final, xfce4 which uses thunar 1.6.6 as its file manager, the file order diplayed is not alphanumeric.  See attached screenshot 
Version-Release number of selected component (if applicable):


How reproducible:always


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Tony Blackwell 2015-05-24 10:27:52 CEST
Created attachment 6627 [details]
screenshot of file order

added screenshot
Comment 2 Tony Blackwell 2015-05-24 10:31:36 CEST
further info
system is installed and running fast on RAID 0, 2 ssd's on a laptop.  Left the original windows install in place, shrank the windows partition and installed M5 after.
Rémi Verschelde 2015-05-24 10:37:32 CEST

Assignee: bugsquad => jani.valimaa

Rémi Verschelde 2015-05-24 10:38:14 CEST

Summary: xfce4 and thunare 1.6.6 disordered file order display => xfce4 and thunar 1.6.6 disordered file order display

Comment 3 Jani Välimaa 2015-05-24 11:05:37 CEST
Created attachment 6630 [details]
Files/folders sorted by name

Your screenshot reveals that files/folders aren't sorted by name (but probably by date modified). There should be a black arrow in the name column when files/folders are sorted by name (see the attachment).
Comment 4 Jani Välimaa 2015-05-24 11:57:58 CEST
Just checked and by default files/folders are sorted by name, so you must have clicked other column name, to change sorting, before clicking root file system in left pane.

Closing as INVALID.

Status: NEW => RESOLVED
Resolution: (none) => INVALID