Samuel Thibault, le lun. 04 sept. 2023 22:59:05 +0200, a ecrit: > I'm on it.
So, as usual it's the combination of two issues that were producing the odd behavior. What was happening is that with xbrlapi installed but brltty-x11 not installed, the xbrlapi startup script would try to run brltty with the BrlAPI braille driver and the AtSpi2 screen driver, but the latter wouldn't load, so brltty would fallback to the "no" screen driver. But that driver was not telling the BrlAPI braille driver that it cannot do much, on the contrary it would tell that it works really well, better than Orca, and thus the BrlAPI braille driver would consume most BrlAPI keypresses. With the AtSpi2 driver installed, it knows to tell exactly when it has good support (e.g. in terminals). It happens that upgrading xbrlapi fixed this because in the newer version the xbrlapi startup script checks that both the BrlAPI and the AtSpi2 drivers are available, and not start that brltty in that case. So, long story short: https://github.com/brltty/brltty/pull/428 and I'll backport some fixes to bookworm. Samuel
