This bug is STILL present. Also, using the proposed workaround "-rfbportv6 -1" does not seem to have any effect. Is the Debian maintainer active with the upstream developers and looking into a fix? The proper solution is to actually make the "-no6" option NOT bind to any IPv6 / tcp6 interface. For instance, in order to fix this bug and verify it, please ensure the following behavior is corrected:
Example: """ # x11vnc -safer -listen 127.0.0.1 -no6 -bg -display :0 2>&1 | egrep -i 'tcp6' 23/07/2014 14:48:42 Autoprobing TCP6 port 23/07/2014 14:48:42 Autoprobing selected TCP6 port 5900 # netstat -plnt | egrep '^tcp6.*/x11vnc' && echo '^^^^ THIS HERE MEANS THE "-no6" OPTION IS NOT WORKING' tcp6 0 0 :::5900 :::* LISTEN 9045/x11vnc ^^^^ THIS HERE MEANS THE "-no6" OPTION IS NOT WORKING """ -- Regards, Kristian Erik Hermansen https://www.linkedin.com/in/kristianhermansen https://google.com/+KristianHermansen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
