Re: brltty input monitor error 19

[Colomban Wendling]

Le 24/01/2024 à 14:14, Samuel Thibault a écrit :

I'd say ask the brltty mailing list. […]


Fair enough :)  I wondered if it being an older Debian version someone 
here would have clues before I bug upstream and they tell me "dunno, try 
latest version first :)", but well, they surely are gonna be most 
knowledgeable indeed.


FWIW, I searched for the term everywhere I could, and only gone 1 fairly 
inconclusive result.


Anyway, I followed you advice and posted there (can share the link 
whenever it pops up), let's see what happens!


Regards,
Colomban

Re: brltty input monitor error 19

[Samuel Thibault]

Hello,

Colomban Wendling, le mer. 24 janv. 2024 12:54:36 +0100, a ecrit:
> 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.

I'd say ask the brltty mailing list. We probably want Dave to add more
information on the actual input device that poses problem. Possibly
we can then filter out such kind of input, or at least understand the
condition in which this does happen (possibly something that gets
unplugged by the user), and react properly.

At least, the brltty mailing list will probably know more if it was seen
previously :)

Samuel

brltty input monitor error 19

[Colomban Wendling]

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 Buster (yeah I know), which is brltty 
5.6.10+deb10u1 [1], not the most recent of all.


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 brltty.


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 there is 
6.3 in the backports, but I'm slightly reluctant to update the client 
just yet unless I can reasonably hope it actually fixes something.


Thanks for your attention, and looking forward to reading you :)
Colomban

[1]: to be entirely honest, it's a custom build from before +deb10u1 got 
released, but it has the exact same patch from Samuel, and diffing the 
sources show no difference apart from the changelog entry
[2]: which is another issue that it can actually happen, but unrelated 
to brltty