I was able to fix this on Fedora by modifying the /etc/hosts file. See
Bug 703009 (https://bugzilla.redhat.com/show_bug.cgi?id=703009).
** Bug watch added: Red Hat Bugzilla #703009
https://bugzilla.redhat.com/show_bug.cgi?id=703009
--
You received this bug notification because you are a
is this actually fixed? I did a yum update vino and it says there is
nothing to update, I am running on Fedora 13 and this is till funding to
the ipv6 only address (do a lsof -i -P | grep -i listen) and you can
see its binding to the ipv6 only and not the ipv4... can someone link me
to how to
** Changed in: vino
Importance: Unknown = Medium
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
workaround/trick:
I don't think this counts as a workaround, since the end functionality
doesn't have any caveats or limitations.
Set these gconf keys in /desktop/gnome/remote_access (I used gconf-editor):
local_only to false
network_interface to lo
Create the key(s) if they don't exist.
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
the number of people in the team is quite slow, most of those
contributing are volunteers which give and hand when they want and there
is over an hundred GNOME packages to work on in several distribution
version, there is just lot of work, the bug could be fixed in hardy but
it would require
So, any possibility to have this problem fixed in Hardy?
* RANT MODE ON *
This is exactly the kind of bugs that drives me mad. This is not some strange
problem in a strange function of a remote piece of code in a seldom used app.
This is a big problem in the remote access tool of the most used
go ahead and back to windows. thank you.
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
mmail wrote:
* RANT MODE ON *
This is exactly the kind of bugs that drives me mad.
This is exactly the kind of comments that will make people go away and do
something else.
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You
Buddy,
if you want better quality and fast solution for solve the problems
found in opensource! don't wait, just work! or following the hint of
Jonh Wendell! back to windows and go ahead!
The patch available at http://bugzilla.gnome.org/show_bug.cgi?id=403192
Thank you!
[]s
--
vino-server
This is exactly the kind of issues that make people go back to Windows.
I started using GNU/Linux 7 years ago and I have seen this kind of
problems too many times, in too many distros. In desktop enviroments in
particular. Bugs that simply should not have made into a stable release.
Bugs that
** Changed in: vino (Debian)
Status: Confirmed = Fix Released
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
** Changed in: vino
Status: Confirmed = Fix Released
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
** Changed in: vino (Ubuntu)
Status: Triaged = Fix Committed
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Patch now available at http://bugzilla.gnome.org/show_bug.cgi?id=403192
Not likely to be fixed in 2.24 which is due too soon according to upstream
maintainer (also needs testing on BSD).
--
vino-server doesn't accept IPv4 connections when local only is checked
I used tightvnc viewer on Windows XP connect to vino on Ubuntu and found
the same problem.
Someone said that this problem may be fixed in version 2.24 but I do not
want to upgrade my Ubuntu. So, I had solved this problem by install IPV6
support on my Windows XP and it work!!!.
--
vino-server
Having the same problem. Is there a workaround for this issue? I have
tried using SSH tunnels using IPv6 addresses explicitly but it doesn't
work.
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification
elventear, to build the tunnel you should run something like this on
your client side:
ssh -L 5910:[::1]:5900 [EMAIL PROTECTED]
Then you should be able to run vncviewer localhost:10
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
** Changed in: vino (Debian)
Status: New = Confirmed
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
This is known upstream and will probably be fixed in 2.24
** Bug watch added: Debian Bug tracker #480863
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480863
** Also affects: vino (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480863
Importance: Unknown
Status:
** Changed in: vino (Debian)
Status: Unknown = New
** Changed in: vino
Status: Unknown = Confirmed
--
vino-server doesn't accept IPv4 connections when local only is checked
https://bugs.launchpad.net/bugs/228370
You received this bug notification because you are a member of Ubuntu
21 matches
Mail list logo
