Ubuntu

GVFS does not resolve to FQDN or IP address

Reported by Howard Williams on 2012-06-28
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gvfs
Invalid
Medium
gvfs (Ubuntu)
Low
Unassigned

Bug Description

Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise

Any package that uses gvfs does not resolve either the FQDN or ip address when trying to mount via ftp.

I have experienced this error in the following packages:

nautilus
gigolo
pcmanfm

I have also gotten this error when using gvfs-mount from the command line.

I have attached a screen shot.

Thank you in advance.

Howard Williams (whwilli) wrote :
description: updated
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in gvfs (Ubuntu):
importance: Undecided → Low
Sebastien Bacher (seb128) wrote :

is that limited to the ftp urls?

Howard Williams (whwilli) wrote :

SSH connections are successful.

Ftp connections generate this error:

$ gvfs-mount ftp://192.168.1.20
Error mounting location: Error resolving '': No address associated with hostname

Webdav generates a similar error:

$ gvfs-mount dav://192.168.1.20
Error mounting location: HTTP Error: Cannot resolve proxy hostname ()

I don't have a Windows Share to test.

After searching and not finding a similar bug, I reported this bug upstream to bugzilla.

https://bugzilla.gnome.org/show_bug.cgi?id=679125

Thank you for your help!

Howard Williams (whwilli) wrote :

I find it strange that the server location is not being passed into the error message.

Sebastien Bacher (seb128) wrote :

what do you get if you run "host 192.168.1.20"? it's a bit weird that the resolving doesn't work for you and it could well be a bug in your network config somewhere

Changed in gvfs (Ubuntu):
status: New → Triaged
Changed in gvfs:
importance: Unknown → Medium
status: Unknown → New
Howard Williams (whwilli) wrote :

I get the following response:

$ host 192.168.1.20
20.1.168.192.in-addr.arpa domain name pointer dev.howardwilliams.com.

and still can not connect with gvfs-mount using ftp.

In my local machine (192.168.1.99) setup I needed to disabled the network-manager dnsmasq resolver by commenting the option in the NetworkManager.conf file and installing dnsmasq. I needed to do this since I have a web server on my local network at 192.168.1.20 and need to access the hosted web sites using their FQDNs. I have used this setup in past versions of ubuntu (natty and lucid) successfully.

I have tried setting the network-manager config back to using the packaged dnsmasq in precise and uninstalling dnsmasq, but it generates the same errors in above posts.

Sebastien Bacher (seb128) wrote :

can you run "gsettings list-recursively org.gnome.system.proxy" and copy the configuration there? the error from comment #4 seems to suggest a misconfigured proxy

Howard Williams (whwilli) wrote :

I found the issue causing the error and it does relate to the proxy settings when using 'auto'.

The configuration below contains org.gnome.system.proxy mode 'auto':

org.gnome.system.proxy autoconfig-url ''
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8']
org.gnome.system.proxy mode 'auto'
org.gnome.system.proxy use-same-proxy false
org.gnome.system.proxy.ftp host ''
org.gnome.system.proxy.ftp port 0
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled false
org.gnome.system.proxy.http host ''
org.gnome.system.proxy.http port 8080
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy.https host ''
org.gnome.system.proxy.https port 0
org.gnome.system.proxy.socks host ''
org.gnome.system.proxy.socks port 0

When I change proxy settings to 'none', gvfs is able to resolve and successfully mount the connection. In the configuration below, note that org.gnome.system.proxy mode is now set to 'none':

org.gnome.system.proxy autoconfig-url ''
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8']
org.gnome.system.proxy mode 'none'
org.gnome.system.proxy use-same-proxy false
org.gnome.system.proxy.ftp host ''
org.gnome.system.proxy.ftp port 0
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled false
org.gnome.system.proxy.http host ''
org.gnome.system.proxy.http port 8080
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy.https host ''
org.gnome.system.proxy.https port 0
org.gnome.system.proxy.socks host ''
org.gnome.system.proxy.socks port 0

It appears that this resolves the problem.

However, we can now only assume Ubuntu 12.04 (Precise) installs with the default proxy setting of 'auto', thus creating this bug.

Thanks again for the help!

Sebastien Bacher (seb128) wrote :

> However, we can now only assume Ubuntu 12.04 (Precise) installs with the default proxy setting of 'auto', thus creating this bug.

no, the default config for that key is 'none' ... you maybe changed it in the proxy config of system settings? it says that "web proxy autodiscovery" is used if the field is let empty

Changed in gvfs:
status: New → Invalid
Camille Acey (joyousnew) wrote :

This resolved my problem as well. My only question is what caused this error all of a sudden? Everything was working normally! I can only imagine it was a recent update...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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