limit to loopback interface doesn't work for ipv6/5800

[Roger Binns]

In dconf I have the network-interface configured to lo (loopback). I use ssh with port forwarding so I don't need or want vino externally accessible. While port 5900 ends up restricted to localhost, port 5800 is not:

$ netstat -an | grep -i tcp | grep -i listen
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:17500 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:17501 0.0.0.0:* LISTEN
tcp6 0 0 :::5800 :::* LISTEN
tcp6 0 0 ::1:5900 :::* LISTEN
tcp6 0 0 :::5298 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 ::1:631 :::* LISTEN
$ lsof -i tcp:5800
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
vino-serv 10382 rogerb 16u IPv6 50199 0t0 TCP *:5800 (LISTEN)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: vino 3.6.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Mon May 13 00:08:23 2013
MarkForUpload: True
SourcePackage: vino
UpgradeStatus: Upgraded to raring on 2013-04-28 (15 days ago)

[Sebastien Bacher (seb128)]

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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.