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 19820 invoked from network); 23 Jan 2022 21:07:41 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 23 Jan 2022 21:07:41 -0000
Received: from 5ess.inri.net ([107.191.111.177]) by 4ess; Sun Jan 23 16:00:02 -0500 2022
Received: from [127.0.0.1] ([104.59.85.219]) by 5ess; Sun Jan 23 15:44:53 -0500 2022
Date: Sun, 23 Jan 2022 20:44:52 +0000
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
In-Reply-To: <33EE949B-EF41-49B7-ADF0-B5E654B11686@stanleylieber.com>
References: <218B2944DD92513F7536ABAEA2CAFD90@wopr.sciops.net> <33EE949B-EF41-49B7-ADF0-B5E654B11686@stanleylieber.com>
Message-ID: <4506D40E-90A8-44A1-BC27-35E002AE6E98@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: non-blocking private API 
Subject: Re: [9front] vncs no longer responding to keyboard
Reply-To: 9front@9front.org
Precedence: bulk

On January 23, 2022 8:43:31 PM UTC, Stanley Lieber <sl@stanleylieber=2Ecom>=
 wrote:
>On January 23, 2022 5:13:52 PM UTC, qwx@sciops=2Enet wrote:
>>On Sun Jan 23 17:10:02 +0100 2022, sl@stanleylieber=2Ecom wrote:
>>> 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 th=
is
>>> >with multiple clients, including vncv (on 9front), tigervnc (on alpin=
e
>>> >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
>>> >
>>>=20
>>> invocation is like this:
>>>=20
>>> vncs -v -g 1920x1080 >>[2]/sys/log/vnc
>>>=20
>>> the error condition produces no error messages, it just doesn't work=
=2E
>>>=20
>>> sl
>>
>>It works fine here for me, both with vncv and vncviewer on linux=2E  I
>>haven't noticed any breakage in my setup=2E  Are you sure there aren't
>>any auth problems?
>>
>>Cheers,
>>qwx
>>
>
>all clients connect fine and i get the gui console and the mouse works, i=
t just doesn't respond to typing=2E if auth wasn't working i would get noth=
ing but an error message, with no gui console displayed=2E
>
>i suppose it's possible something is out of whack with different parts of=
 the system being in different states of current-ness=2E i'll rebuild and t=
ry again=2E
>
>sl
>
>
>
>
>

vncs is running on an rpi4, in case that would matter=2E

sl