[Bug 598597] Re: Vinagre closes connection to tightvncserver 2.0 beta4 immediately

[Steve Beattie]

Correcting the package this bug is against from vinagre to gtk-vnc,
since that's where the underlying problem is. Attached is a debdiff
based on the diffs pointed out by Josh Wendell and mccurrly above for a
lucid SRU.

** Patch added: "gtk-vnc_0.3.10-2ubuntu2.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/598597/+attachment/2281557/+files/gtk-vnc_0.3.10-2ubuntu2.1.debdiff

** Changed in: vinagre (Ubuntu)
   Importance: Undecided => Medium

** Package changed: vinagre (Ubuntu) => gtk-vnc (Ubuntu)

** Description changed:

  Binary package hint: vinagre
  
  Ubuntu 10.04 (Lucid), Vinagre 2.30.2-0ubuntu1
  When I connect to a TightVNC-Server 2.0 beta4 the conntection closes immediately with
  "Connection to host <ip> was closed."
  Other VNC-Viewers are working without a problem.
+ 
+ SRU Justification:
+ Bug prevents gtk-vnc based clients from working with upcoming tightvncserver releases.
+ 
+ Risk of regression:
+ Low, patch is a one-line change from upstream only affecting the version string sent in response to the server.
+ 
+ Testcase:
+ 1) Install tightvncserver v2 (not yet in Ubuntu or Debian repositories, alas)
+ 2) start tightvncserver session
+ 3) connect to it with vinagre or another gtk-vnc client; client should attach successfully.

-- 
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/598597

Title:
  Vinagre closes connection to tightvncserver 2.0 beta4 immediately

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk-vnc/+bug/598597/+subscriptions