file-roller does not respect sort order for folders
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
File Roller |
Invalid
|
Undecided
|
Unassigned | ||
file-roller (Ubuntu) |
Low
|
Unassigned |
Bug Description
Binary package hint: file-roller
file-roller displays files and folders in an archive as multi-column list. Clicking a column title sorts it ascending, clicking it again sorts it descending. It behaves like Nautilus, except that folders are always sorted according to their name column!
I'd expect that files and folders are both sorted according to the same column, the last-clicked column that shows the small arrow to indicate the sort order.
I checked file-roller 2.30.1.1-0ubuntu2 (updated Lucid) and 2.31.90-0ubuntu1 (Maverick beta1 CD) - both are affected.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: file-roller 2.31.90-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Fri Sep 24 16:42:59 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: file-roller
Oliver Joos (oliver-joos) wrote : | #1 |
Changed in file-roller: | |
importance: | Unknown → Low |
status: | Unknown → New |
Changed in file-roller (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
dino99 (9d9) wrote : | #2 |
Changed in file-roller (Ubuntu): | |
status: | Triaged → Invalid |
Changed in file-roller: | |
importance: | Low → Undecided |
status: | New → Invalid |
Oliver Joos (oliver-joos) wrote : | #3 |
I confirm that this bug still exists in file-roller 3.6.3 of 12.04 LTS.
If I click on the Date column only files are sorted by date, folders stay sorted by their name.
Changed in file-roller: | |
importance: | Undecided → Unknown |
status: | Invalid → Unknown |
Oliver Joos (oliver-joos) wrote : | #4 |
Sorry, I meant file-roller 3.6.3 in Ubuntu Raring 13.04 is still affected.
Changed in file-roller (Ubuntu): | |
status: | Invalid → Confirmed |
dino99 (9d9) wrote : | #5 |
hi Oliver,
as you can see, that report is about "maverick" , aka gnome2 old time; meaning no one works and will not on that oldish code, even if an gnome2 upstream report exist. That it.
Thats said, you can send a new report about gnome3; you'll get better chance to grab a possible fix if you also report it upstream.
So i'm closing that useless one, sorry.
Changed in file-roller (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in file-roller: | |
importance: | Unknown → Undecided |
status: | Unknown → New |
status: | New → Invalid |
Oliver Joos (oliver-joos) wrote : | #6 |
I know, I was the initial reporter. I don't understand the advantage of opening a new report, but here it is: bug 1185735
Please help setting it to "Triage" like this bug was since 2010.
BTW: I already reported it upstream (see Remote Watch).
EOL reached on that serie https:/ /wiki.ubuntu. com/Releases