Bug 1394 - pcmanfm does not list files and folders in any order
Summary: pcmanfm does not list files and folders in any order
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: check
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-05-23 04:46 CEST by You-Cheng Hsieh
Modified: 2012-01-05 11:03 CET (History)
1 user (show)

See Also:
Source RPM: pcmanfm-0.9.8-4.mga1
CVE:
Status comment:

Attachments
pcmanfm screenshot (651.44 KB, image/png)
2011-06-17 12:50 CEST, You-Cheng Hsieh 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description You-Cheng Hsieh 2011-05-23 04:46:58 CEST 
Description of problem:
pcmanfm, the default file manager of lxde, does not list files and folders in any specific order, neither name, size, time, nor file type.


Version-Release number of selected component (if applicable):
0.9.8-4.mga1

How reproducible:
Always

Steps to Reproduce:
1.Install pcmanfm
2.Start pcmanfm
3.Browse any directories, see if you can figure out any order in default files and folder list.
Comment 1 Ahmad Samir 2011-06-16 22:53:49 CEST 
Could you post a screen shot?

Keywords: (none) => NEEDINFO

Comment 2 You-Cheng Hsieh 2011-06-17 12:50:51 CEST 
Created attachment 576 [details]
pcmanfm screenshot

Reproduced in LXDE.
Comment 3 Manuel Hiebel 2011-10-11 12:45:39 CEST 
Hi, is the issue still valid ? (it works here)

Version: Cauldron => 1
Whiteboard: (none) => check

Comment 4 Manuel Hiebel 2011-11-20 00:50:43 CET 
ping ?
Comment 5 Marja Van Waes 2012-01-05 11:03:17 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => marja11
Note You need to log in before you can comment on or make changes to this bug.