Skip to content

Can't connect to NFS resources

In gigolo 0.5.0 (probably many earlier versions) NFS resources are treated as Custom Locations and incorrectly handled, so that

  • a bookmarked NFS location can't be connected ("Mount point does not exist");
  • the Connect dialogue doesn't accept a valid NFS URL as a Custom Location ("You must enter a server address or name."). The lists shown in Help>Supported Protocols, the Connect>Service Type pull-down and the output of gigolo -l (ie, what the backend supports) are all different, and NFS isn't shown in the first 2, so a NFS resource has to be a Custom Location.

Apparently the program is confused about how to parse a Custom Location URL into the fields used for connecting and bookmarking.

$ man gigolo
... 
       -l, --list-schemes
                 Print a list of supported URI schemes and exit.
...
$ gigolo -l
...
nfs
...
$ gio mount nfs://example.local/mount/point && echo yes
yes
$

Now nfs://example.local/mount/point appears in Gigolo with Name point on example.local.

This item (with the actual valid server name and mount point) can be bookmarked in Gigolo. Disconnect and try to connect using Actions>Bookmarks; after Connecting ... for a while, the connection fails with Mount point does not exist. Using Edit>Edit Bookmarks>Edit, the bookmarked URL is shown with no mount path (eg nfs://example.local/).

Instead try to connect using Actions>Connect with Service type: Custom Location and the NFS URL in the Location (URI) field; on OK the dialogue fails with You must enter a server address or name..