Limited functionality in Unity file browser
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
New
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: unity
In the new unity netbook interface I'm able to get the file browser to show up when I click on the folder icon. (The applications button, on the other hand, doesn't work, due to Bug #629692.) Once I launch the file browser however, there is very limited functionality. I can left-click on a file or folder to open it, and the back button next to the search bar seems to work OK, but that's about it. Right-clicking has no effect on files or folders, so I can't do things like copy, cut, paste, or sort.
Also, if I move to another window, the unity launcher indicates that the folder view is still running (there is a triangle to the left of the icon), I can't go back to whatever folder view I had by clicking on the Files & Folders icon again. (The first click usually does nothing, and clicking again brings back the home screen.)
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: unity 0.2.34-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Tue Sep 7 18:12:51 2010
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcEnviron:
LANG=en_CA.utf8
SHELL=/bin/bash
SourcePackage: unity
Thanks for your bug report Sean. The original plan for Maverick was to just land the "file browsing" feature, not full "file management".
For Natty we'll probably expand the scope to include a bit of file management features you request. To my knowledge there hasn't been detailed design thoughts on this yet. I think we definitely don't want to implement a full file manager inside Unity, that's just way too complex, just include the very basic tasks you'd expect to be able to do.
I can't promise on what we'll be able to deliver, but I'd like it if you'd share a prioritized list of the features you miss the most?
(regarding bug #629692 I am glad to say I pushed a fix to trunk just yesterday :-))