GNOME Bugzilla – Bug 593205
Cannot connect to avahi-advertised shares
Last modified: 2009-10-26 18:51:15 UTC
I can no longer connect to shares advertised over avahi. I'm testing with latest 2.27.x vinagre/vino on ubuntu and fedora rawhide. I can however still connect fine manually (with IP).
Please, run vinagre in a terminal with the argument --gtk-vnc-debug and paste here the output. Thanks.
$ vinagre --gtk-vnc-debug gtk-vnc: Expose 0x0 @ 1011,863 gtk-vnc: Started background coroutine gtk-vnc: Resolving host pandora.local 5900 gtk-vnc: Failed to resolve hostname gtk-vnc: Doing final VNC cleanup gtk-vnc: Requesting that VNC close gtk-vnc: Requesting that VNC close gtk-vnc: Releasing VNC widget In vinagre, I get this error message: --- Connection closed Connection to host monreal's remote desktop on pandora was closed --- Vino on pandora is configured to accept connection from anywhere without any password or confirmation and there is (currently) no firewall active.
What's the result of ping pandora.local? This seems to be a dns/avahi fail, not a vinagre issue...
ping: unknown host pandora.local Notice that avahi-discover shows all hosts on the local net and also shows the correct IPs (in the "Address" field). Does vinagre rely on avahi writing discovered hostnames to resolf.conf or something? I don't know if it is supposed to do this, but at least it does not work that way on both Ubuntu and Fedora... I think vinagre should get the actual IP from avahi and use this to connect.
commit a986583ba8b7f6a144238298a89d6aa19c03ebb2 Author: Jonh Wendell <jwendell@gnome.org> Date: Sun Sep 6 09:36:50 2009 -0300 Show IP addresses of avahi-discovered machines instead of names. For instance, show 10.0.0.1 instead of wendell-laptop.local. Closes #593205.
*** Bug 586938 has been marked as a duplicate of this bug. ***