[BRLTTY] brltty input monitor error 19

[Colomban Wendling]

Hello Zachary & all,

Le 24/01/2024 à 19:40, Zachary Kline a écrit :
> I'm not familiar with this error but it would help to provide info
> about the specific braille device they are using. Which display is it
> and how is it connected to the machine?

Indeed I should have included this from the get go: it's a USB Basic 
Braille from HandyTech.

> The sheer number of messages is rather concerning but suggests
> something bluetooth related, or perhaps some sort of faulty hardware,
> in one form or another.

I'll look closer tomorrow, but I just peeked at the logs I have to see 
if it looked like a flickering device, and it does -- at least in some 
occurence (the device getting connected for 3 seconds, then for a couple 
more, repeated a couple times).  That might indeed be a cable, plug or 
device issue.

Still a bit scray brltty would get *so* upset, but the proper fix might 
lie in hardware.

I'll look at more log occurrences tomorrow (it's fairly long given the 
amount to go through) to see if it all correlates.

Thanks,
Colomban

> 
> Sent from my iPhone
> 
>> On Jan 24, 2024, at 10:06 AM, Colomban Wendling
>> <cwendling at hypra.fr> wrote:
>> 
>> Hello everyone,
>> 
>> A client of mine is having trouble with brltty sometimes heavily
>> spamming the logs with "braille input monitor error 19: No such
>> device", and I'm wondering what this could actually mean is the
>> trouble.
>> 
>> Also, by spamming I mean like a lot, for the last week alone he's
>> got more than 17 million lines matching that in syslog (~500k one
>> day, 9.1M another, and 7.6M yesterday).  When it happens, it spams
>> insanely fast, I can count around 50k messages/second for about 5s
>> at a time.
>> 
>> The client is running Debian 10 "Buster" (yeah I know, it's not
>> up-to-date), which is brltty 5.6.10+deb10u1 [1].
>> 
>> As a workaround, I currently set "log-level critical" to try and
>> not get these errors in the logs, as their rate managed to fill
>> /var/log [2]; and because the client didn't seem to actually have
>> issues with his braille device.
>> 
>> Does anybody here have clues on: * why does it happen?  Is
>> something *actually* wrong, just going unnoticed by the user? * was
>> it a bug that has been fixed in newer releases?  I know the client
>> isn't using the latest version, but I'm slightly reluctant to
>> update it just yet unless I can reasonably hope it actually fixes
>> the issue.
>> 
>> Thanks for your attention, and looking forward to reading you :) 
>> Colomban
>> 
>> [1]: This is brltty 5.6.10 with a few Debian patches -- mostly
>> backports of specific relevant commits IIUC
>> (https://salsa.debian.org/a11y-team/brltty/-/tree/debian-buster/debian/patches?ref_type=heads)
>>
>> 
[2]: which is another issue that it can actually happen, but unrelated 
to brltty
>> _______________________________________________ This message was
>> sent via the BRLTTY mailing list. To post a message, send an e-mail
>> to: BRLTTY at brltty.app For general information, go to:
>> http://brltty.app/mailman/listinfo/brltty
> 
> _______________________________________________ This message was sent
> via the BRLTTY mailing list. To post a message, send an e-mail to:
> BRLTTY at brltty.app For general information, go to:
> http://brltty.app/mailman/listinfo/brltty