Bug 5548 - Filemanager for LXDE Magelia2 beta 3 Dual Arch CD problem with sorting in X86_64
Summary: Filemanager for LXDE Magelia2 beta 3 Dual Arch CD problem with sorting in X86_64
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-22 03:24 CEST by jon scsi
Modified: 2012-04-23 07:23 CEST (History)
1 user (show)

See Also:
Source RPM: pcmanfm
CVE:
Status comment:


Attachments

Description jon scsi 2012-04-22 03:24:01 CEST
Description of problem:
LXDE's filemanager in X86_64 cannot or will-not sort files/directories in any order other than default, trying to change settings does nothing

Version-Release number of selected component (if applicable):
Mageia 2 Beta 3 Dual Arch CD

How reproducible:
always

Steps to Reproduce:
1.Tools>System tools>filemanager
2.View>sort files> ascending+byname (or any other combo not currently in use)
3.no change in the display window
Remco Rijnders 2012-04-22 07:04:11 CEST

Assignee: bugsquad => oliver.bgr

Comment 1 Oliver Burger 2012-04-22 10:45:08 CEST
John: I can't reproduce. Works perfectly here..

Bugsquad: Please reassign to pcmanfm maintainer, thanks!

CC: (none) => oliver.bgr
Assignee: oliver.bgr => bugsquad

Remco Rijnders 2012-04-22 11:13:18 CEST

Assignee: bugsquad => lists.jjorge
Source RPM: LXDE => pcmanfm

Comment 2 José Jorge 2012-04-22 21:53:16 CEST
I can't reproduce too.

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

Comment 3 jon scsi 2012-04-23 07:23:58 CEST
blast, tried on my two X86_64 boxes with same problem showing both places before adding it in too. Wonder what i'm doing wrong!

I've also just checked the iso for hashcode in case there was something, but to no avail it matches.

ok, thanks all, I must be doing something wrong, sooner i'm stable and back in my qt4 configuration the better.

Note You need to log in before you can comment on or make changes to this bug.