Le 05/03/2021 à 02:23, Dave Mielke a écrit :
> [quoted lines by Didier Spaier on 2021/03/05 at 01:03 +0100]
>
>>> Thanks to Tony, here goes: https://slint.fr/brltty/brltty.log
>>
>> Do you need more information to investigate?
>
> As I think I said, at the time, that log showed brltty terminating
properly
> when receiving SIGTERM. What I need is a log that sows brltty failing to
> terminate on SIGTERM.
No, I don't remember you said that. I have uploaded a file twice in the
same location (with the same name, hence maybe the misunderstanding),
did you look there after the second time? If I remember correctly Tony
killed it with a SGKILL not a SIGTERM. Tonny, do you confirm?
Anyway Philippe (in CC) reproduced the issue, but this time brltty not
starting by a script, but only by udev.
In the use case alsobrltty works in the console but not through Orca.
Additionally, from a tty:
1. Killing brltty with SIGTERM leads to no input on the device, but the
brltty process remains.
2. Starting brltty again starts a second process, but the device still
gets no input
3. Then 'killal -9 brltty' works and starting brltty the device gets
the expected input.
I can still request a debug log in this context, and mount / read-write
from start just editing a line in grub.cfg, but then how should I modify
the udev rules to include the debug options? Should I modify udev.rules
or udev-wrapper and how?
Best regards
Didier
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.app/mailman/listinfo/brltty
