After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 324036 - File Dialog widget fails to work with filesystems which require typing in a directory name to mount a directory
File Dialog widget fails to work with filesystems which require typing in a d...
Status: RESOLVED DUPLICATE of bug 136541
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
unspecified
Other All
: Normal major
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2005-12-14 03:10 UTC by Richard Deken
Modified: 2006-04-13 02:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Richard Deken 2005-12-14 03:10:28 UTC 
The GTK File Dialog widget fails to work with filesystems which require typing
in a directory name to mount a directory.  Our company uses an automount
filesystem on /net which mounts remote NFS servers when /net/servername is used
in a path.  The GTK File Dialog widget fails to provide any mechanism for
working with these types of file systems.  Further it is impracticle to setup
the file systems to automatically query all hosts on the network (tens of
thousands) on our network and mount all of them run with NFS exports.  Please
provide some method of working with these types of filesystems in the file
dialog widget.  Thanks.

Other information:
Comment 1 Owen Taylor 2005-12-14 16:05:56 UTC 
Basically, asking your (less experienced) users to type in the path to 
the mount they need is a bad idea; configure a bookmark for them instead.
An entry where someone has to type a mystic path that they can't browse
to doesn't quite count as discoverable.

For experienced users, I don't think it is awful that they can just start
typing /net and get a dialog where they can enter the path.

(If you don't buy this, and think that we *have* to have an entry visible
by default, well, there is bug where you can go pile on with everybody 
else, though that generally isn't productive.)

I think the last time someone complained I retitled the bug to 
something like "provide system-wide config file for bookmarks",
but I can't find that bug. Either it's been fixed or I just can't
find it.
Comment 2 Federico Mena Quintero 2006-04-13 02:33:07 UTC 
Fixed in the federico-file-name-entry branch.  I'll merge this to HEAD soon.  In the meantime, I'll mark this as a duplicate of the "we need a filename entry" bug.

*** This bug has been marked as a duplicate of 136541 ***