From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by ewsd; Sat Feb  2 08:14:09 EST 2019
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
	by mailout.west.internal (Postfix) with ESMTP id 970F62D95
	for <9front@9front.org>; Sat,  2 Feb 2019 08:14:07 -0500 (EST)
Received: from web3 ([10.202.2.213])
  by compute1.internal (MEProxy); Sat, 02 Feb 2019 08:14:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h=
	message-id:from:to:mime-version:content-transfer-encoding
	:content-type:references:subject:in-reply-to:date; s=fm2; bh=lEH
	UwpIRwUAkhgIJu8oDt07xMp2yCtQFaVW7wF0iaec=; b=ZktB0wIpX50ValRTP5M
	a4qGMeu+HUziX6Bkf1DyhJV5ih8gZ9z/QlKB34LOJXxttsMSGoEB+87jLzWaVQhJ
	p7zMf+rGyeIpftiCtmffyq0mGsRaMVMKKW8CwYQXxFBBSWMRKGpt4QO+dXCi0iPG
	lpjCmWNRz/nDT21TjA2yQuzTNTFl4cWenhfvPd1LYmAMacabyr3tHOXQFOWPBnNi
	fCdRkjQs99wagUAJsB6qmYA6WHsMnVZAVgrPkYR+3AdLOoUQ2nuAnMK9aiuockRL
	djEqrhMIN7ZncS67MA+bdpYw6et7soTAZkNzhhX5aFeBw68nyN+cHoXT0ZDjQriW
	8Lg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
	:x-sasl-enc; s=fm1; bh=lEHUwpIRwUAkhgIJu8oDt07xMp2yCtQFaVW7wF0ia
	ec=; b=MM/iQBVcxqpElgZyjPu4NH1d19wp8iL4MIwYDFT8xG6dmK9qsuCNfz7Gp
	y/zpXCXfDG8uISpQ/a1ah1VsVqUbZxuNDLs5A5aKXaM6ML9HWGJhPuIokuUQb7af
	XzPwqzhcWGGkYxtkFjyH3SEXY2jcsrA2mlkI8Gy8tio7cinVIL/0AsRx1bTs2151
	/TNJQsWpJuVDVA3YBXKDk1HUqIhBVWD30kxVmGoxt7vYswcgJIWVUSNupzjA6V9U
	17qvAGsQM0bSX2/nrTOyOfzQ4nQ1BUt3cvHf3OeXYgb5nciZqLbsH1eYA6ZUS3xy
	BoQx+UoUQbCkJ+z2+xQgYZeOzQpbQ==
X-ME-Sender: <xms:npdVXKhOJ1EQe30YHPvrgejXKPoFMBcXVyKeAnFLTzMd6IJebhyFBA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrkedtgdehtdcutefuodetggdotefrodftvf
    curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt
    tdenucenucfjughrpefkhffvggfgtgfofhfujgffsehtjeertdertdejnecuhfhrohhmpe
    fgthhhrghnucfirghruggvnhgvrhcuoegvvghkvggvheejsehfrghsthhmrghilhdrfhhm
    qeenucfrrghrrghmpehmrghilhhfrhhomhepvggvkhgvvgehjeesfhgrshhtmhgrihhlrd
    hfmhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:n5dVXOVb2QfAubkUZvwGN_pliG8ak--M7GspQ579YiFhVFpw4wHOJQ>
    <xmx:n5dVXGKIb_sCTOv0ybAkeMKXsMq4fXj9ZwHdJIzJak6gWgZf5jFRBA>
    <xmx:n5dVXJpnLC5FSnLO9d0W5UgyxVFdjGzW8IuTIlfFykSgz-_A-pEGDQ>
    <xmx:n5dVXFf13IBJ8DiP8YhtGDUZhqpnDyjJ4WD8mMHWh49Xxrz_4Ifdog>
Received: by mailuser.nyi.internal (Postfix, from userid 99)
	id BA26E9E539; Sat,  2 Feb 2019 08:14:06 -0500 (EST)
Message-Id: <1549113246.2990995.1649262184.54888F5D@webmail.messagingengine.com>
From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-ec01da05
References: <90792F84B66CE28B8F654484B130BD75@felloff.net>
Subject: Re: [9front] vncs: some clients report 'bad hextile data' -- workaround
 found
In-Reply-To: <90792F84B66CE28B8F654484B130BD75@felloff.net>
Date: Sat, 02 Feb 2019 13:14:06 +0000
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: session injection content-driven optimizer 

On Thu, Jan 31, 2019, at 6:04 PM, cinap_lenrek@felloff.net wrote:
> not sure if this is really a issue with the hextile encoding. you could
> comment out the EncHextile case in setencoding() in vncs.c to exclude it.

Did this, it works now.  On my LAN there's no perceptible delay or anything, so it can stay like this.

Funnily enough, with hextile disabled, RealVNC 6.19 works better than 6.17.  Pale colors disappear in 6.17.  Maybe they broke hextile when they fixed that bug, or something.

It's no wonder Unix VNC servers and clients have so many options.