GNOME Bugzilla – Bug 679125
gvfs can not resolve hostname
Last modified: 2012-06-29 14:51:12 UTC
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 plain ip addresses when trying to mount via ftp and webdav. I have experienced this error in the following packages: nautilus gigolo pcmanfm I am receiving the following errors from the command line: SSH connections: Connect without error. OK FTP connections get the following error: $ gvfs-mount ftp://192.168.1.20 Error mounting location: Error resolving '': No address associated with hostname Webdav connections get the following 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. This error appears using both FQDN and plain ip addresses. FQDN are being resolved when using nslookup. Thank you in advance, Howard
(In reply to comment #0) > $ gvfs-mount dav://192.168.1.20 > Error mounting location: HTTP Error: Cannot resolve proxy hostname () Looks like badly set proxy address. Try changing to "Direct connection".
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!
no, the default is 'none', you can select "auto" in g-c-c though and the ui says that if no url is entered then "web proxy autodiscovery" is used... maybe that feature is not working?