From owner-freebsd-questions@FreeBSD.ORG  Sun Jan  3 22:04:04 2010
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0F2C41065676
	for <freebsd-questions@freebsd.org>;
	Sun,  3 Jan 2010 22:04:04 +0000 (UTC)
	(envelope-from runge@karlrunge.com)
Received: from holmes.jfku.edu (holmes.jfku.edu [66.117.151.7])
	by mx1.freebsd.org (Postfix) with ESMTP id D64998FC1C
	for <freebsd-questions@freebsd.org>;
	Sun,  3 Jan 2010 22:04:03 +0000 (UTC)
Received: from haystack.runge.home (runge@localhost [127.0.0.1])
	by holmes.jfku.edu (8.9.3p3.JFKU/8.9.1) with ESMTP id OAA23433;
	Sun, 3 Jan 2010 14:03:35 -0800
Received: from runge by haystack.runge.home with local (Exim 3.36 #1 (Debian))
	id 1NRYXu-0008K7-00; Sun, 03 Jan 2010 17:03:34 -0500
To: wblock@wonkity.com
In-Reply-To: Mail from 'Warren Block <wblock@wonkity.com>'
	dated: Sun, 3 Jan 2010 14:31:46 -0700 (MST)
From: "Karl J. Runge" <runge@karlrunge.com>
Message-Id: <E1NRYXu-0008K7-00@haystack.runge.home>
Date: Sun, 03 Jan 2010 17:03:34 -0500
Cc: freebsd-questions@freebsd.org
Subject: Re: Remote assistance for X
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jan 2010 22:04:04 -0000

On Sun, 3 Jan 2010, Warren Block wrote:
> >
> > I believe a workaround for you will be:
> >
> >    ssvncviewer -listen -rfbversion 3.7
> >
> > this reverts to the previous protocol version where there is no issue.
> 
> Confirmed, that works fine with TightVNC servers from both of the 
> Windows systems.  Thanks!

Very good.

The bug fix for this is now in the the dev source tarball:

	http://ssvnc.sourceforge.net/dev/ssvnc-1.0.26.src.tar.gz

in case you or anyone else wants to test that it works.  This should
work with TightVNC servers without the need for -rfbversion.