All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Alexander Epaneshnikov <aarnaarn2@gmail.com>
Cc: qemu-devel@nongnu.org, brltty@brltty.app
Subject: Re: baum: NVDA does not detect usb-braille, and following the input-linux grab
Date: Sun, 18 Oct 2026 21:17:03 +0200	[thread overview]
Message-ID: <atUbL22N4UounO8L@end> (raw)
In-Reply-To: <atUU4HpVVI59QcLJ@alex-pc>

Alexander Epaneshnikov, le dim. 18 oct. 2026 21:52:44 +0300, a ecrit:
> On Sun, Oct 18, 2026 at 06:26:53PM +0200, Samuel Thibault wrote:
> > I'm a bit surprised by setting the priority to 0, but maybe that's
> > because of your setup, which is not described enough. Are you
> > running on the linux console or X, actually?
> 
> Sorry, I should have described it. The host runs GNOME on Wayland on
> tty 2, with Orca using BrlAPI.
> 
> The guest is a Windows VM started by libvirt, with a second GPU passed
> through to it. My monitor is connected to both GPUs. I switch its input
> by hand, or over DDC/CI when I need sighted help. QEMU itself has no
> window: the display is "none", and SPICE has no listener. I am blind,
> so in practice I use the guest through NVDA's speech, which comes out
> through PipeWire on the host, and its braille.
> 
> > But then how do you access the VM to get keyboard/mouse access?
> 
> Through input-linux (libvirt <input type='evdev'> with grab='all').
> QEMU reads the host keyboard and mouse evdev devices directly. Pressing
> both Ctrl keys toggles the exclusive grab between the host and the
> guest.

So you mean that you make qemu steal keyboard presses from under your
Wayland session? That is very peculiar... I'm really unclear this way of
stealing the keyboard will work on the long run.

> There is no front-end. The grab toggle happens inside QEMU's
> input-linux, so QEMU is the only process that knows which side has the
> keyboard. libvirt doesn't see it, and neither does anything else on
> the host. That is why I thought baum should react to it directly.

I now understand your situation, but I don't think it is long-term
sustainable :/

> > SDL/GTK do not need a grab: provided that the window id is properly
> > set, brlapi already switches according to the window focus.
> 
> Thanks, that answers my third question. Then only input-linux, which
> has no window, needs to report the grab.

Yes, this is really a situation only for such tinkering.

Samuel


  parent reply	other threads:[~2026-10-18 19:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <atNoDNz0dQucxzFN@alex-pc>
     [not found] ` <atNo9sk_7jCAi98u@end>
2026-10-17 19:13   ` baum: NVDA does not detect usb-braille, and following the input-linux grab Alexander Epaneshnikov
2026-10-18 16:26     ` Samuel Thibault
2026-10-18 18:52       ` Alexander Epaneshnikov
2026-10-18 19:10         ` baum: NVDA does not detect usb-braille Samuel Thibault
2026-10-18 19:35           ` Alexander Epaneshnikov
2026-10-18 20:49             ` Samuel Thibault
2026-10-18 19:17         ` Samuel Thibault [this message]
2026-10-18 19:26           ` baum: NVDA does not detect usb-braille, and following the input-linux grab Alexander Epaneshnikov
2026-10-18 19:30             ` Samuel Thibault
2026-10-18 19:39               ` Alexander Epaneshnikov

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=atUbL22N4UounO8L@end \
    --to=samuel.thibault@ens-lyon.org \
    --cc=aarnaarn2@gmail.com \
    --cc=brltty@brltty.app \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.