GNOME Bugzilla – Bug 622539
Connection to TightVNC 2.0 beta server closes immediately
Last modified: 2010-07-16 15:18:21 UTC
I've been trying out TightVNC 2.0 betas on various Windows servers and am unable to use vinagre to connect to them. When I try to connect to any of them I immediately get a dialog box saying "Connection closed - Connection to host XXXX was closed."
I can confirm that the problem is still there with vinagre-2.30.0-1.fc13.i686 and tightvnc 2.0.2 (on fedora 13). Tobias
Please confirm what version of gtk-vnc you have installed, and also capture a debug log using vinagre --gtk-vnc-debug host:display If practical, also please test the latest gtk-vnc 0.4.0 build.
This is with gtk-vnc-0.3 tobias@tobslap:~$ rpm -q gtk-vnc gtk-vnc-0.3.10-3.fc13.i686 tobias@tobslap:~$ vinagre --gtk-vnc-debug winxp gtk-vnc: Expose 0x0 @ 1266,677 gtk-vnc: Started background coroutine gtk-vnc: Resolving host winxp 5900 gtk-vnc: Trying socket 20 gtk-vnc: Protocol initialization gtk-vnc: Server version: 3.8 gtk-vnc: Using version: 3.8 gtk-vnc: Closing the connection: gvnc_read() - ret=0 gtk-vnc: Auth failed gtk-vnc: Doing final VNC cleanup gtk-vnc: Requesting that VNC close gtk-vnc: Delayed unref 0x91bc098 1 gtk-vnc: Requesting that VNC close gtk-vnc: Releasing VNC widget After yum erase gtk-vnc-0.3.10-3.fc13.i686 and deps (including vinagre) I install the koji build of gtk-vnc and gvnc with rpm --install gtk-vnc-0.4.0-1.fc14.i686.rpm gvnc-0.4.0-1.fc14.i686.rpm and reinstall vinagre with yum install vinagre. Now i have: gtk-vnc-0.4.0-1.fc14.i686 gvnc-0.4.0-1.fc14.i686 vinagre-2.30.0-1.fc13.i686 and I get this trace: tobias@tobslap:~$ vinagre --gtk-vnc-debug winxp (vinagre:7840): gvnc-DEBUG: vncconnection.c Init VncConnection=0x95dc720 gtk-vnc: vncdisplaykeymap.c Using evdev keycode mapping (vinagre:7840): gvnc-DEBUG: vncconnection.c Open host=winxp port=5900 gtk-vnc: vncdisplay.c Expose area 1266x677 at location 0,0 (vinagre:7840): gvnc-DEBUG: vncconnection.c Open coroutine starting (vinagre:7840): gvnc-DEBUG: vncconnection.c Started background coroutine (vinagre:7840): gvnc-DEBUG: vncconnection.c Resolving host winxp 5900 (vinagre:7840): gvnc-DEBUG: vncconnection.c Trying socket 20 (vinagre:7840): gvnc-DEBUG: vncconnection.c Emit main context 12 gtk-vnc: vncdisplay.c Connected to VNC server (vinagre:7840): gvnc-DEBUG: vncconnection.c Protocol initialization (vinagre:7840): gvnc-DEBUG: vncconnection.c Server version: 3.8 (vinagre:7840): gvnc-DEBUG: vncconnection.c Using version: 3.8 (vinagre:7840): gvnc-DEBUG: vncconnection.c Possible auth 2 (vinagre:7840): gvnc-DEBUG: vncconnection.c Possible auth 16 (vinagre:7840): gvnc-DEBUG: vncconnection.c Emit main context 10 (vinagre:7840): gvnc-DEBUG: vncconnection.c Thinking about auth type 2 (vinagre:7840): gvnc-DEBUG: vncconnection.c Decided on auth type 2 (vinagre:7840): gvnc-DEBUG: vncconnection.c Waiting for auth type (vinagre:7840): gvnc-DEBUG: vncconnection.c Choose auth 2 (vinagre:7840): gvnc-DEBUG: vncconnection.c Do Challenge (vinagre:7840): gvnc-DEBUG: vncconnection.c Requesting missing credentials (vinagre:7840): gvnc-DEBUG: vncconnection.c Emit main context 9 (vinagre:7840): gvnc-DEBUG: vncconnection.c Set credential 0 oct00ant (vinagre:7840): gvnc-DEBUG: vncconnection.c Waiting for missing credentials (vinagre:7840): gvnc-DEBUG: vncconnection.c Got all credentials (vinagre:7840): gvnc-DEBUG: vncconnection.c Checking auth result (vinagre:7840): gvnc-DEBUG: vncconnection.c Success (vinagre:7840): gvnc-DEBUG: vncconnection.c Pixel format BPP: 32, Depth: 24, Byte order: 1234, True color: 1 Mask red: 255, green: 255, blue: 255 Shift red: 16, green: 8, blue: 0 (vinagre:7840): gvnc-DEBUG: vncconnection.c Display name 'winxp-tob' (vinagre:7840): gvnc-DEBUG: vncconnection.c Emit main context 13 gtk-vnc: vncdisplay.c Using default colour depth 24 (32 bpp) (true color? 1) vinagre: symbol lookup error: /usr/lib/libgtk-vnc-1.0.so.0: undefined symbol: gdk_image_get_visual So I tried to install the latest vinagre in koji, but that requires a newer telepathy-glib. Before my system ends up being rawhide I give up... Tobias
The bug you get vinagre: symbol lookup error: /usr/lib/libgtk-vnc-1.0.so.0: undefined symbol: gdk_image_get_visual is because you tried to install an F14 RPM on F13, without updating GTK to the F14 version. To avoid this you'd actually need to rebuild the 0.4.0 src.rpm for F13. That aside though, this 0.4.0 trace clearly gets alot further, all the way to setting up the framebuffer, whereas the 0.3.10 trace is terminated immediately after sending the protocol version. This makes me suggest that this patch from 0.4.0 is what solved it: http://git.gnome.org/browse/gtk-vnc/commit/?id=bc9e2b19167686dd381a0508af1a5113675d08a2 I will try and test a tightvnc server to verify. If you want this fixed in Fedora 13 updates, please do file a BZ against Fedora and refer to this BZ.
Ok, I've confirmed that this particular changeset fixed the problem with TightVNC. This was included in 0.4.0, so marking this fixed.
Thanks Daniel for the quick replies ! I filed a bug with fedora: https://bugzilla.redhat.com/show_bug.cgi?id=615350 Tobias