vinagre fails to connect to any VNC server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gtk-vnc (Ubuntu) |
Fix Released
|
High
|
Mathieu Trudel-Lapierre | ||
Maverick |
Fix Released
|
High
|
Mathieu Trudel-Lapierre | ||
vinagre (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Maverick |
Invalid
|
High
|
Unassigned |
Bug Description
Binary package hint: vinagre
The version of vinagre in Maverick fails to connect to VNC servers, merely returning "Connection to host xxx was closed" before even asking for the passphrase. The Lucid version works file. Ssh connections seem to work fine.
The easiest way to reproduce this problem is by doing the following:
- Enable the vino VNC server in System > Preferences > Remote Desktop,
by ticking "Allow other users to view your desktop"; untick all three
"security" options to make things easy.
- Open vinagre in Applications > Internet > Remote Desktop Viewer
- Click "Connect", and select "VNC", enter 127.0.0.1 as the host, and
make sure "Fullscreen" and "Use host xxx as SSH tunnel" are both off.
The above fails on Maverick, while it worked on Lucid. I have also tried to connect to two actual VNC hosts (running vino on Lucid, FWIW), which also fails. xvnc4viewer works on the Maverick machine, so it's a vinagre problem.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: vinagre 2.30.2-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Thu Sep 9 23:36:12 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: vinagre
Related branches
- Martin Pitt: Approve
-
Diff: 222 lines (+202/-0)3 files modifieddebian/changelog (+8/-0)
debian/patches/lp634571_auth_subtype_logic_fix.patch (+193/-0)
debian/patches/series (+1/-0)
Changed in vinagre (Ubuntu): | |
status: | New → Confirmed |
tags: | added: patch |
Changed in vinagre (Ubuntu Maverick): | |
milestone: | none → ubuntu-10.10 |
This bug is reminiscent of bug #206227, by the way, in case there's any relation.