[BRLTTY] BRLTTY floods the log with the Freedom Scientific Focus Blue

Alex ARNAUD aarnaud at hypra.fr
Tue Nov 24 13:27:59 EST 2020


When the Focus Blue is unplugged I have the following message in the log 
every second:
> brltty[3417]: brltty: polkit_authority_check_authorization_sync error: 
> GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process 
> subject does not have uid set


Le 24/11/2020 à 19:23, Alex ARNAUD a écrit :
>
>>> Based on our tests, the Braille device works.
>> Which tests?  On the same computer with Linux, or with some other OS?
> I meant the user was able to use the Focus Blue on his computer on 
> Debian 10.
>
>> Also, is the user actually using the device?
> The user uses both speech and Braille with Orca, yes, but it seems he 
> relies  primarily on speech.
>
>>> Moving the log level to emergency doesn't seem to have produce any effects.
>> Which log level?  There are more log levels involved here.  What the
>> kernel reports, and what BRLTTY will log.
> I meant BRLTTY log level.
>
>>> Defining the log file to /tmp/brltty.log continues to pollute the syslog and
>>> daemon.log.
>>>
>>> What can we do to improve the situation? Currently we've unplugged the Focus
>>> Blue and stop BRLTTY.
>> Again, was the user actually using the device?  If it was properly
>> functioning, I wonder why BRLTTY was apparently retrying to initialize
> I confirm, BRLTTY seems to disconnect/reconnect to the device, the 
> user see the message BRLTTY 6.1 then it works again. It is quite 
> similar of what I see on my Seika device when it is plugged to the 
> computer.
>
>> the device again and again.  Could it be that more then just one BRLTTY
>> were trying to fight over the same device?  IOW, did you check that only
>> one instance of BRLTTY was running?
> A "ps aux |grep -i brltty" gives me only one instance of BRLTTY running.
>
> Restarting the computer with the Braille display plugged makes it 
> working and after some times of usage the issue occur again.
>
> Just new log I found (I give you not only BRLTTY log because I don't 
> really understand them and I would like to provide you the most 
> informations as possible):
>> xhci_hcd 0000:00:14.0: Trying to add endpoint 0x1 without dropping it.
>> kernel: [ 2826.939008] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> brltty[3417]: brltty: USB language code string read error
>> brltty[3417]: brltty: USB configuration set error 22: Argument invalide
>> brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB configuration descriptor not readable: 0
>> brltty[3417]: brltty: USB configuration descriptor not found: 1
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> kernel: [ 2831.939098] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> kernel: [ 2831.939394] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> kernel: [ 2831.939651] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> kernel: [ 2831.939748] xhci_hcd 0000:00:14.0: Trying to add endpoint 
>> 0x1 without dropping it.
>> kernel: [ 2831.939931] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> brltty[3417]: brltty: USB language code string read error
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB language code string read error
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB language code string read error
>> brltty[3417]: brltty: USB configuration set error 22: Argument invalide
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB configuration descriptor not readable: 0
>> brltty[3417]: brltty: USB configuration descriptor not found: 1
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB language code string read error
>> kernel: [ 2836.939094] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> kernel: [ 2836.939393] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> kernel: [ 2836.939649] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> kernel: [ 2836.939748] xhci_hcd 0000:00:14.0: Trying to add endpoint 
>> 0x1 without dropping it.
>> kernel: [ 2836.939925] usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd 
>> brltty rqt 128 rq 6 len 255 ret -71
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB language code string read error
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB language code string read error
>> brltty[3417]: brltty: USB configuration set error 22: Argument invalide
>> brltty[3417]: brltty: USB control transfer error 71: Erreur de protocole
>> brltty[3417]: brltty: USB configuration descriptor not readable: 0
>> brltty[3417]: brltty: USB configuration descriptor not found: 1
>> kernel: [ 2841.831084] usb 1-5: USB disconnect, device number 43
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20201124/393c60d6/attachment.html>


More information about the BRLTTY mailing list