Bug#596287: vinagre fails to connect to VNC server
reassign 596287 libgtk-vnc-1.0-0 affects 596287 vinagre thanks It seems you're not the first to find this problem: http://mail.gnome.org/archives/gtk-vnc-list/2010-September/msg0.html The workaround there doesn't seem like a good solution in general to me. I've tried debugging this a bit and I think the problem lies in the signal handling of gtk-vnc, rather then vinagre. If I've understood gtk-vnc correctly, it has a vnc connection and a vnc display object. The connection signals vnc-auth-credential which the display object subscribes to (on_auth_cred). The display object then sends the same signal, to anyone (vinagre) that subscribes to vnc-auth-credential on the display object. When running this in a debugger I think on_auth_cred is never called and thus the signal on the vnc display object that vinagre subscribes to is never emitted. Reading symbols from /opt/vinagre/bin/vinagre...done. (gdb) run Starting program: /opt/vinagre/bin/vinagre [Thread debugging using libthread_db enabled] ^C Program received signal SIGINT, Interrupt. 0x72ca10d8 in __poll (fds=0x7af210, nfds=11, timeout=value optimized out) at ../sysdeps/unix/sysv/linux/poll.c:83 83 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. in ../sysdeps/unix/sysv/linux/poll.c (gdb) break on_auth_cred Breakpoint 1 at 0x7fffedf1114a: file vncdisplay.c, line . (gdb) c Continuing. The above scenario: gdb vinagre run break the execution with ctrl-c add breakpoint continue click in vinagre and attempt connection. breakpoint never hit and connection failed dialog shown. Breaking on do_vnc_connection_emit_main_context works and the breakpoint gets hit. no idea why the signals never surface. Another test case is to eliminate vinagre by using examples/gvncviewer.py and observing that it also never calls the vnc_auth_cred, which is the function subscribed to the credentials signal on the vnc display object in the example. -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596287: vinagre fails to connect to VNC server
found 596287 0.4.1-3 fixed 596287 0.3.10-6 thanks This is a regression compared to gtk-vnc 0.3.10 which I've confirmed working (after rebuilding it from http://snapshot.debian.org/package/gtk-vnc/0.3.10-6/ and rebuilding vinagre with 0.3.10 installed). Here's the vinagre debug output when running with gtk-vnc 0.3.10 where apparently TLS+password authentication works... $ vinagre --gtk-vnc-debug gtk-vnc: Expose 0x0 @ 440,390 gtk-vnc: Started background coroutine gtk-vnc: Resolving host 127.0.0.1 5900 gtk-vnc: Trying socket 18 gtk-vnc: Protocol initialization gtk-vnc: Server version: 3.7 gtk-vnc: Using version: 3.7 gtk-vnc: Possible auth 18 gtk-vnc: Possible auth 2 gtk-vnc: Thinking about auth type 18 gtk-vnc: Decided on auth type 18 gtk-vnc: Waiting for auth type gtk-vnc: Choose auth 18 gtk-vnc: Do TLS handshake gtk-vnc: Handshake was blocking gtk-vnc: Handshake was blocking gtk-vnc: Handshake was blocking gtk-vnc: Handshake done gtk-vnc: Completed TLS setup gtk-vnc: Got 1 subauths gtk-vnc: Got 1 subauths gtk-vnc: Possible sub-auth 2 gtk-vnc: Requested auth subtype 2 gtk-vnc: Waiting for auth subtype gtk-vnc: Choose auth 2 gtk-vnc: Do Challenge gtk-vnc: Requesting missing credentials gtk-vnc: Set password credential seahorse gtk-vnc: Waiting for missing credentials gtk-vnc: Got all credentials gtk-vnc: Checking auth result gtk-vnc: Expose 0x77 @ 268,199 gtk-vnc: Success gtk-vnc: 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 gtk-vnc: Display name 'g...@amd64' gtk-vnc: Setting depth color to 24 (32 bpp) gtk-vnc: Visual mask: 16711680 65280 255 shift: 16 8 0 gtk-vnc: Mask local: 255 255 255 remote: 255 255 255 merged: 255 255 255 gtk-vnc: Pixel shifts right: 16 8 0 left: 16 8 0 [...] -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596287: vinagre fails to connect to VNC server
git bisect told me the gtk-vnc credentials signalling issue was because of http://git.gnome.org/browse/gtk-vnc/commit/?id=4395a9aeb59651f0daa868bfcf0060e2f60d8098 I can't spot anything obviously wrong there.. There's a small typo in sigdata.params.authCred = authTypes; which should probably be sigdata.params.authTypes = authTypes; but it doesn't really matter since both of them are in the same union anyway. For background on the problem see: http://bugs.debian.org/596287 As a testcase ./examples/gvncviewer localhost (where localhost is running vino) was used and a password prompt = success, connection closed = failure. Hopefully Daniel P. Berrange can help shed some light on what might be the cause? -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596287: vinagre fails to connect to VNC server
retitle 596287 Fails to connect to vino forwarded 596287 gtk-vnc-list gnome org thanks On Sat, Sep 11, 2010 at 04:29:28PM +0200, Andreas Henriksson wrote: reassign 596287 libgtk-vnc-1.0-0 affects 596287 vinagre thanks It seems you're not the first to find this problem: http://mail.gnome.org/archives/gtk-vnc-list/2010-September/msg0.html The workaround there doesn't seem like a good solution in general to me. This was just a quick hack to get it working. I didn't have any time to look into this yet. -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596287: vinagre fails to connect to VNC server
On Thu, Sep 09, 2010 at 08:20:52PM -0400, Andres Cimmarusti wrote: I've been using vino as vnc server on this computer. Lately I haven't been able to connect to the server using vinagre while using remmina works fine. I get a pop-up message saying connection to server has been closed. It doesn't even prompt me for password. Please attach the console debug output you get when running vinagre --gtk-vnc-debug and attempting to connect. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596287: vinagre fails to connect to VNC server
$ vinagre --gtk-vnc-debug (vinagre:9384): gvnc-DEBUG: vncconnection.c Init VncConnection=0x8988000 gtk-vnc: vncdisplaykeymap.c Using evdev keycode mapping (vinagre:9384): gvnc-DEBUG: vncconnection.c Open host=phonon port=5900 gtk-vnc: vncdisplay.c Expose area 438x408 at location 0,0 (vinagre:9384): gvnc-DEBUG: vncconnection.c Open coroutine starting (vinagre:9384): gvnc-DEBUG: vncconnection.c Started background coroutine (vinagre:9384): gvnc-DEBUG: vncconnection.c Resolving host phonon 5900 (vinagre:9384): gvnc-DEBUG: vncconnection.c Trying socket 18 (vinagre:9384): gvnc-DEBUG: vncconnection.c Emit main context 12 gtk-vnc: vncdisplay.c Connected to VNC server (vinagre:9384): gvnc-DEBUG: vncconnection.c Protocol initialization (vinagre:9384): gvnc-DEBUG: vncconnection.c Server version: 3.7 (vinagre:9384): gvnc-DEBUG: vncconnection.c Using version: 3.7 (vinagre:9384): gvnc-DEBUG: vncconnection.c Possible auth 18 (vinagre:9384): gvnc-DEBUG: vncconnection.c Possible auth 2 (vinagre:9384): gvnc-DEBUG: vncconnection.c Emit main context 10 (vinagre:9384): gvnc-DEBUG: vncconnection.c Thinking about auth type 18 (vinagre:9384): gvnc-DEBUG: vncconnection.c Decided on auth type 18 (vinagre:9384): gvnc-DEBUG: vncconnection.c Waiting for auth type (vinagre:9384): gvnc-DEBUG: vncconnection.c Choose auth 18 (vinagre:9384): gvnc-DEBUG: vncconnection.c Do TLS handshake (vinagre:9384): gvnc-DEBUG: vncconnection.c Handshake was blocking (vinagre:9384): gvnc-DEBUG: vncconnection.c Handshake was blocking (vinagre:9384): gvnc-DEBUG: vncconnection.c Handshake was blocking (vinagre:9384): gvnc-DEBUG: vncconnection.c Handshake was blocking (vinagre:9384): gvnc-DEBUG: vncconnection.c Handshake done (vinagre:9384): gvnc-DEBUG: vncconnection.c Completed TLS setup (vinagre:9384): gvnc-DEBUG: vncconnection.c Got 1 subauths (vinagre:9384): gvnc-DEBUG: vncconnection.c Got 1 subauths (vinagre:9384): gvnc-DEBUG: vncconnection.c Possible sub-auth 2 (vinagre:9384): gvnc-DEBUG: vncconnection.c Emit main context 10 (vinagre:9384): gvnc-DEBUG: vncconnection.c Thinking about auth type 2 (vinagre:9384): gvnc-DEBUG: vncconnection.c Auth failed (vinagre:9384): gvnc-DEBUG: vncconnection.c Doing final VNC cleanup (vinagre:9384): gvnc-DEBUG: vncconnection.c Close VncConnection=0x8988000 (vinagre:9384): gvnc-DEBUG: vncconnection.c Emit main context 14 gtk-vnc: vncdisplay.c Disconnected from VNC server gtk-vnc: vncdisplay.c Display destroy, requesting that VNC connection close gtk-vnc: vncdisplay.c Display destroy, requesting that VNC connection close gtk-vnc: vncdisplay.c Releasing VNC widget (vinagre:9384): gvnc-DEBUG: vncconnection.c Delayed unref VncConnection=0x8988000 (vinagre:9384): gvnc-DEBUG: vncconnection.c Finalize VncConnection=0x8988000 On Fri, Sep 10, 2010 at 5:56 AM, Andreas Henriksson andr...@fatal.se wrote: On Thu, Sep 09, 2010 at 08:20:52PM -0400, Andres Cimmarusti wrote: I've been using vino as vnc server on this computer. Lately I haven't been able to connect to the server using vinagre while using remmina works fine. I get a pop-up message saying connection to server has been closed. It doesn't even prompt me for password. Please attach the console debug output you get when running vinagre --gtk-vnc-debug and attempting to connect. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596287: vinagre fails to connect to VNC server
Package: vinagre Version: 2.30.2-1 Severity: grave Justification: renders package unusable I've been using vino as vnc server on this computer. Lately I haven't been able to connect to the server using vinagre while using remmina works fine. I get a pop-up message saying connection to server has been closed. It doesn't even prompt me for password. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vinagre depends on: ii gconf2 2.28.1-3 GNOME configuration database syste ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libavahi-common30.6.27-2 Avahi common library ii libavahi-gobject0 0.6.27-2 Avahi GObject library ii libavahi-ui00.6.27-2 Avahi GTK+ User interface library ii libbonobo2-02.24.3-1 Bonobo CORBA interfaces library ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-5 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst ii libdbus-glib-1-20.88-2 simple interprocess messaging syst ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.4.2-1 FreeType 2 font engine, shared lib ii libgconf2-4 2.28.1-3 GNOME configuration database syste ii libglib2.0-02.24.1-1 The GLib library of C routines ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libgtk-vnc-1.0-00.4.1-2 A VNC viewer widget for GTK+ (runt ii libgtk2.0-0 2.20.1-1+b1 The GTK+ graphical user interface ii libpanel-applet2-0 2.30.2-1 library for GNOME Panel applets ii libpango1.0-0 1.28.1-1 Layout and rendering of internatio ii libtelepathy-glib0 0.11.11-1Telepathy framework - GLib library ii libvte9 1:0.24.3-1 Terminal emulator widget for GTK+ ii libx11-62:1.3.3-3X11 client-side library ii libxml2 2.7.7.dfsg-4 GNOME XML library vinagre recommends no packages. vinagre suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
