I think this bug can be closed, I'm pretty sure it is related to the
bindv6only /proc parameter which was set by default at that time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/196675
Title:
vin
** Changed in: vino
Importance: Unknown => Medium
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
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.c
Vladimir, go to a terminal and type ifconfig. Find out which interface
is your loopback. In my machine it is "lo". Put that interface in the
vino gconf key.
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You received this bug notification because you are a member
John,
You mentioned it's enough to set the key
/desktop/gnome/remote_access/network_interface to "lo".
Could you clarify what is it enough for, specifically?
I did this and on my PC it is still listening on tcp6 :::5900 allowing other
machines to connect. I have boxes on the same subnet and they
Em Sáb, 2009-04-25 às 17:36 +, Maverick88 escreveu:
> Jonh -- It sounds like you must now run gconf-edito to be able to
> restrict the vino vnc server to accept only local connections. If you
> do that, can you still connect to vino via an SSH tunnel? It sounds
> like you can now.
Sure. It'
Jonh -- It sounds like you must now run gconf-edito to be able to
restrict the vino vnc server to accept only local connections. If you
do that, can you still connect to vino via an SSH tunnel? It sounds
like you can now.
Can you also confirm that this bug was fixed in Hardy Heron 8.04 LTS?
If
That feature was replaced by the new gconf key:
/desktop/gnome/remote_access/network_interface
Run gconf-editor and browse that directory in order to read the documentation
on how it works.
And yes, I've removed the 'advanced' tab. 'Advanced' users know to ho
use gconf-editor to tunning applicat
I'm not sure how this is fixed.
I'm looking at Jaunty 9.04 Alpha 5 with vino 2.25.91, and it seems that
the user interface has changed and no longer includes the option to
allow only local connections. In fact, the whole "advanced" tab is gone.
So it's fixed by completely removing functionality?
This bug was fixed in the package vino - 2.25.91-0ubuntu1
---
vino (2.25.91-0ubuntu1) jaunty; urgency=low
* New upstream release (LP: #330215)
- Install autostart file in $sysconfdir/xgd/autostart. Usually you
should pass the argument --sysconfdir=/etc to configure (or
** Changed in: vino (Ubuntu)
Status: Triaged => Fix Committed
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Changed in: vino
Status: Confirmed => Fix Released
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
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.
Hmm, sorry. After some further investigations I can confirm that vino doesn't
accept connections with "only allow local".
However, this seems to be fixed upstream since a couple of days ago.
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You received this bug no
oh, somewhat newer than the original post.
[EMAIL PROTECTED]:~$ apt-cache policy vino
vino:
Installed: 2.24.1-0ubuntu1
Candidate: 2.24.1-0ubuntu1
Version table:
*** 2.24.1-0ubuntu1 0
500 http://se.archive.ubuntu.com intrepid/main Packages
100 /var/lib/dpkg/status
It could d
Ambricka,
what the version of vino that you using for test?
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
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.
No problem connecting with ipv4 here, even though my netstat -tlp looks similar.
A bigger problem for me is when I'm only reachable via ipv6 and the host isn't
listed in dns I can't connect with vinagre which doesn't accept raw ipv6 host
addresses. (Or am I just wrong in the ipv6 notation?)
--
** Changed in: vino
Status: Unknown => Confirmed
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
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.ubunt
** Changed in: vino (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: Confirmed => Triaged
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: vino via
http://bugzilla.gnome.org/show_bug.cgi?id=403183
Importance: Unknown
Status: Unknown
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Hi,
if you known, try apply the last patch found in
http://bugzilla.gnome.org/show_bug.cgi?id=403183
becouse this patch solve this problem, and next release fixed this problem!
[]s
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You received this bug notific
When you select to allow only local connections, it listens on ::1,
which doesn't seem to allow tcp4 connections to 127.0.0.1. The
workaround is to allow all connections and implement firewall rules.
This is very annoying for those expecting "local" connections to be from
remote hosts, like when u
Possible upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=403183
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
I am unable to connect via IPv4 (Hardy).
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
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://l
(though I can still connect on ipv4...)
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
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://li
Confirmed for version 2.22.1-1.
tcp6 0 0 ::1:5901:::*LISTEN
32592/vino-server
** Changed in: vino (Ubuntu)
Importance: Undecided => Low
Status: Incomplete => Confirmed
--
vino only listens for ipv6 connections
https://bugs.launc
I can connect from a IPv4 IP (127.0.0.1). I think tcp6 includes IPv4 tcp
as well. Have you tried running "vncviewer 127.0.0.1" from a terminal?
** Changed in: vino (Ubuntu)
Status: New => Incomplete
--
vino only listens for ipv6 connections
https://bugs.launchpad.net/bugs/196675
You recei
25 matches
Mail list logo
