From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 16959 invoked from network); 23 Jan 2022 16:13:02 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 23 Jan 2022 16:13:02 -0000
Received: from 5ess.inri.net ([107.191.111.177]) by 4ess; Sun Jan 23 11:05:03 -0500 2022
Received: from [127.0.0.1] ([104.59.85.219]) by 5ess; Sun Jan 23 10:27:00 -0500 2022
Date: Sun, 23 Jan 2022 15:26:58 +0000
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
In-Reply-To: <6D18EFDAAFAA55DDB2088D534B93572C@5ess.inri.net>
References: <6D18EFDAAFAA55DDB2088D534B93572C@5ess.inri.net>
Message-ID: <806B38AF-065A-4593-A440-344D66496A5E@stanleylieber.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: descriptor scripting information-oriented solution 
Subject: Re: [9front] vncs no longer responding to keyboard
Reply-To: 9front@9front.org
Precedence: bulk

On January 23, 2022 4:44:59 AM UTC, sl@stanleylieber=2Ecom wrote:
>not sure when this broke, but keystrokes from vnc clients (9front or
>otherwise) are no longer recognized by 9front vncs=2E  i've tested this
>with multiple clients, including vncv (on 9front), tigervnc (on alpine
>linux), and jump (on android), all with the same behavior=2E  i can
>connect fine, the mouse works, but no matter what i type there is no
>response from the 9front gui console (rio has not been started yet)=2E
>
>this used to work, i used it all the time=2E
>
>sl
>

invocation is like this:

vncs -v -g 1920x1080 >>[2]/sys/log/vnc

the error condition produces no error messages, it just doesn't work=2E

sl