This bug was fixed in the package gobby - 0.4.9-1
---
gobby (0.4.9-1) unstable; urgency=low
* New upstream release
* Add a build-dependency on intltool which is now used to translate
the desktop file.
* Tighten the build-dependency on net6 to get newer templates.
(LP: #3
Will be fixed soonish in Jaunty.
--
gobby only listens for ipv6 connections
https://bugs.launchpad.net/bugs/313393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
You are right, it does work!
# nmap localhost -p6522 | grep open
6522/tcp open unknown
Man, I was blindly trusting netstat/lsof, guess I've learned something
today.
Thanks for fixing it anyway, it might save someone from the same
confusion.
--
gobby only listens for ipv6 connections
https://b
Have you tried connecting with IPv4 nevertheless? I also see only the
IPv6 listening socket in netstat, but can connect on both IPv4 and IPv6.
--
gobby only listens for ipv6 connections
https://bugs.launchpad.net/bugs/313393
You received this bug notification because you are a member of Ubuntu
Bu
Wow, that was lightning fast, thank you for the fix!
The workaround looked promising but bindv6only=0 is the default here too.
Changing it made no difference for gobby/vino:
# sysctl net.ipv6.bindv6only=0
net.ipv6.bindv6only = 0
# sysctl net.ipv6.bindv6only=1
net.ipv6.bindv6only = 1
r...@dingsdal
I just fixed this upstream:
http://git.0x539.de/?p=net6.git;a=commit;h=04ede417257b3201b68b683d13a69e07f8401eb8
Until this hits Ubuntu, you can probably set
/proc/sys/net/ipv6/bindv6only to 0 to get IPv4 connectivity. (This seems
to be the default on my machine, by the way, which is why I didn't
n
