Re: [Bug 206227] Re: vinagre fails to connect
Martin Pitt wrote: gtkglext promoted to main. Please reopen if there are still problems with building this. What's the fix in 0.3.6? Can it be backported to hardy? It was supposed to be debian/patches/from_upstream_fix_vinagre_connection_lp_206227.patch (see comment 24) Jonh, do you have a clue why it didn't work? The hg repo seems to be down right now, so I can't check if there was more related commits... -- vinagre fails to connect https://bugs.launchpad.net/bugs/206227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 206227] Re: vinagre fails to connect
interim_descriptor wrote: I don't know what the process for this is, but somebody in Ubuntu should really consider pushing this fix into a Hardy Heron update. I opened bug 218667 for updating gtk-vnc for Hardy, but it was too late and it introduced some regressions so this won't probably hit hardy-updates unfortunately. Unless we can backport a non-intrusive patch for them, without updating gtk-vnc entirely. -- vinagre fails to connect https://bugs.launchpad.net/bugs/206227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 206227] Re: vinagre fails to connect
Matthew Tighe wrote: Is this fix going to make into Hardy or Hardy.1? Unfortunately it won't, as this requires a new version of gtk-vnc which we won't introduce at this stage. If not, I think you should simply remove it. It doesn't really work. I'm sorry it doesn't work for this case, but it works for others. Also, you can install xvncviewer on your own, so I don't think we should change it as it's now the official GNOME client and we should give it a chance and support it. For Intrepid, it will be much better and won't have any regressions compared to xvncviewer. -- vinagre fails to connect https://bugs.launchpad.net/bugs/206227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 206227] Re: vinagre fails to connect
Jonh Wendell [EMAIL PROTECTED] writes: James, could you please paste here the output of xvnc4viewer with that machine? | $ xvnc4viewer localhost:5900 | | VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04 | Copyright (C) 2002-2005 RealVNC Ltd. | See http://www.realvnc.com for information on VNC. | | Wed Apr 2 18:27:43 2008 | CConn: connected to host localhost port 5900 | | Wed Apr 2 18:27:44 2008 | CConnection: Server supports RFB protocol version 4.0 | CConnection: Using RFB protocol version 3.8 | | Wed Apr 2 18:27:47 2008 | TXImage: Using default colormap and visual, TrueColor, depth 24. | CConn: Using pixel format depth 6 (8bpp) rgb222 | CConn: Using ZRLE encoding | CConn: Throughput 2 kbit/s - changing to hextile encoding | CConn: Throughput 2 kbit/s - changing to full colour | CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 | CConn: Using hextile encoding | zsh: exit 1 xvnc4viewer localhost:5900 | $ (The 'localhost' is because I'm ssh port forwarding to the machine which is several networks away.) -- James -- vinagre fails to connect https://bugs.launchpad.net/bugs/206227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
