nautilus does not recognize any server type

Bug #1617107 reported by lucas
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus with ssh, sftp, nsf, dav, really anything I can think of gives "This file server type is not recognized." Error message appears as soon as : is entered, e.g. "ssh:".

ssh and sftp work just fine from the command line.

using nautilus version "Files 3.14.3"

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, it works fine here though. Could you add you syslog to the bug and the output of "dpgk -l | grep gvfs"?

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
lucas (parra) wrote :

That is what I was afraid of.

dmesg -w does not report anything new when I get the error message. Any other way of reporting syslog that would be helpful?

dpkg -l |grep gvfs
ii gvfs:amd64 1.28.2-1ubuntu1~16.04.1 amd64 userspace virtual filesystem - GIO module
ii gvfs-bin 1.28.2-1ubuntu1~16.04.1 amd64 userspace virtual filesystem - binaries
ii gvfs-common 1.28.2-1ubuntu1~16.04.1 all userspace virtual filesystem - common data files
ii gvfs-daemons 1.28.2-1ubuntu1~16.04.1 amd64 userspace virtual filesystem - servers
ii gvfs-fuse 1.28.2-1ubuntu1~16.04.1 amd64 userspace virtual filesystem - fuse server
ii gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1 amd64 userspace virtual filesystem - private libraries

PS: I did install sshfs after the new install to no avail. Not sure that matters. Also tested if this is a permission issue by running the same as guest user. Same problem.

Revision history for this message
Sebastien Bacher (seb128) wrote :

hum, does "ftp" give you the same issue? can you use gvfs-mount ftp://ftp.debian.net, does it work? can you use gvfs-ls on it then? (or same with a ssh host)

Revision history for this message
lucas (parra) wrote :

gvfs-mount ftp://ftp.debian.net
Error mounting location: Location is not mountable

Revision history for this message
lucas (parra) wrote :

just in case

sudo gvfs-mount ftp://ftp.debian.net
Error mounting location: volume doesn't implement mount

in case it matters:

mount | grep gvfs
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Revision history for this message
Sebastien Bacher (seb128) wrote :

urg, I misread the dpkg -l output, looks like you are simply missing gvfs-backends ... does installing that fixes your issue?

Revision history for this message
lucas (parra) wrote :

by the way, thanks for your help on this! just in case, some more data points:

sudo gvfs-mount ftp://ftp.debian.net
Error mounting location: volume doesn't implement mount

nad in case it matters:

mount | grep gvfs
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Revision history for this message
lucas (parra) wrote :

yup! that did it, after reboot. you are the best!

Strange that this was not installed by default with 16.04. As I said, I did a clean install. At any rate. Thanks!

Revision history for this message
Sebastien Bacher (seb128) wrote :

weird, gvfs-backends is on the default installation for sure, see e.g http://cdimage.ubuntu.com/daily-live/current/yakkety-desktop-amd64.manifest

can you add you /var/log/dpkg.log* to the bug?

Revision history for this message
lucas (parra) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

the log has

2016-08-14 12:18:20 remove gvfs-backends:amd64 1.28.2-1ubuntu1~16.04.1 <none>

seems it has been uninstalled at the same time as deja-dup-backend-gvfs but the log doesn't give info on what actions leaded those to be removed but it seems post installation since your log has older entries that show it installed

Revision history for this message
lucas (parra) wrote :

Totally my fault! Now I remember, when I first installed 16.04 I removed it as it was chewing up CPU time and battery and it was not clear to me for what it is needed. Now I know what I need it for! Sorry to have burdened you. It is well behaved now though.

Revision history for this message
Sebastien Bacher (seb128) wrote :

k, it makes sense now! closing the bug then, for the record the cpu usage was likely bug #1572260

Changed in nautilus (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.