From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] vncs no longer responding to keyboard
Date: Sun, 23 Jan 2022 20:43:31 +0000 [thread overview]
Message-ID: <33EE949B-EF41-49B7-ADF0-B5E654B11686@stanleylieber.com> (raw)
In-Reply-To: <218B2944DD92513F7536ABAEA2CAFD90@wopr.sciops.net>
On January 23, 2022 5:13:52 PM UTC, qwx@sciops.net wrote:
>On Sun Jan 23 17:10:02 +0100 2022, sl@stanleylieber.com wrote:
>> On January 23, 2022 4:44:59 AM UTC, sl@stanleylieber.com wrote:
>> >not sure when this broke, but keystrokes from vnc clients (9front or
>> >otherwise) are no longer recognized by 9front vncs. i've tested this
>> >with multiple clients, including vncv (on 9front), tigervnc (on alpine
>> >linux), and jump (on android), all with the same behavior. 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).
>> >
>> >this used to work, i used it all the time.
>> >
>> >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.
>>
>> sl
>
>It works fine here for me, both with vncv and vncviewer on linux. I
>haven't noticed any breakage in my setup. 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, it just doesn't respond to typing. if auth wasn't working i would get nothing but an error message, with no gui console displayed.
i suppose it's possible something is out of whack with different parts of the system being in different states of current-ness. i'll rebuild and try again.
sl
next prev parent reply other threads:[~2022-01-23 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 4:44 sl
2022-01-23 15:26 ` Stanley Lieber
2022-01-23 17:13 ` qwx
2022-01-23 20:43 ` Stanley Lieber [this message]
2022-01-23 20:44 ` Stanley Lieber
2022-01-23 21:54 ` sl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33EE949B-EF41-49B7-ADF0-B5E654B11686@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).