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 383307 - Gnome filechooser doesn't understand NFS-root
Gnome filechooser doesn't understand NFS-root
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
unspecified
Other All
: Normal minor
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2006-12-07 10:05 UTC by steven.mccoy
Modified: 2018-04-15 00:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description steven.mccoy 2006-12-07 10:05:57 UTC 
Please describe the problem:
On a HDD install the Gnome/Gtk file open/save dialog shows a "File System" link and the path buttons have an arrow to navigate up the tree. On NFS-root there is no "File System" and the button which used to have an arrow now doesn't.

Steps to reproduce:
1. Setup NFS root machine
2. Run Gtk 2 application, e.g. gedit
3. Select "Open"


Actual results:
http://librarian.launchpad.net/5311069/Screenshot-NFS-root.png

Expected results:
http://librarian.launchpad.net/5311068/Screenshot-HDD-root.png

Does this happen every time?
Yes

Other information:
Logged in Launchpad with screenshots:

https://bugs.launchpad.net/distros/ubuntu/+source/gtk+2.0/+bug/74790
Comment 1 Matthias Clasen 2018-02-10 04:58:24 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:07:01 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new