[BRLTTY] Workaround for wrong Orca session detection

[Julian]

Hello,

oh, I didn't realize that. Sure, I'll keep the list in CC.

Yes, we're passing the USB device through. This is possible by 
downloading and compiling a kernel module available on SourceForge (yes, 
this is the official VMware documentation).

Attached are the logs, copied from /tmp/brltty.log (I enabled the 
corresponding config first). I hope this brings us any further.

Kind regards, Julian

Am 09.10.22 um 21:16 schrieb Samuel Thibault:
> Hello,
>
> Please keep the list in Cc, so the discussion can be archived and useful
> for everybody.
>
> Julian, le sam. 08 oct. 2022 19:32:17 +0200, a ecrit:
>> Well no, I didn't install the OS myself. The VM pool is on a server, and I'm
>> connecting to it using my laptop and a dedicated VMware client
> Ah, ok, so it's indeed a very special situation.
>
> I'm however wondering: how do you get Braille output? Are you passing
> through a Braille device?
>
>> Anyway, I found a workaround that makes the connection work: First I have to
>> stop the brltty-udev service that was automatically spawned, and then launch
>> brltty manually with the switch -x auto.
> It would be useful to see the brltty logs, to see why the brltty-udev
> service doesn't manage to accept BrlAPI connections, while the manual
> start does.
>
> Samuel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: brltty.log
Type: text/x-log
Size: 3752 bytes
Desc: not available
URL: <http://brltty.app/pipermail/brltty/attachments/20221011/48149f5e/attachment.bin>