Bug#935484: brltty flooding syslog with error messages - DBus error: send message: org.freedesktop.DBus.Error.NoReply

[DM]

Hello Samuel,
Yes, it would be preferable not to flood the logs, however in this particular case, things got so strange, I still can't narrow down how exactly this situation happen.
The device that caused this, was connected to the system via USB bus, there was no explicit messages from kernel regarding the unidentified device. OS for some very strange reason, right after the very first boot after installation, enabled all kind of the futures for blind persons and persons hard of hearing... speech/voice over got turned on by a default for example.
As soon as this 'usb module / component' was removed, all the weirdness and strange behavior of OS was gone. No errors in logs, normal boot and shutdown with out any delays.
This makes me to think that there was more involved issue rather than just 'brltty' spamming logs. Perhaps on a kernel level?
This is beyond my level of expertise.

Damien




‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, August 23, 2019 11:21 AM, Samuel Thibault <samuel.thibault at ens-lyon.org> wrote:

> Samuel Thibault, le ven. 23 août 2019 09:56:06 +0200, a ecrit:
>
> > As reported by a Debian user:
> > skyguide via Pkg-a11y-devel, le jeu. 22 août 2019 21:14:11 -0700, a ecrit:
> >
> > > brltty is flooding syslog with error messages.
> > > brltty[422]: brltty: DBus error: send message: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms
> > > brltty[422]: DBus error: send message: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken
> > > brltty[422]: brltty: DBus error: send message: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken
> > > Those messages keeps spamming /var/log/syslog casing it to grow aoutof control.
> > > Please note that this happens on a fresh/new install of Debian 10 Buster, on a hardware with no bluetooth hardware installed.
> > > Please advise how this can be stopped/corrected.
>
> DM via Pkg-a11y-devel, le ven. 23 août 2019 10:17:13 +0000, a ecrit:
>
> > Hello, please close this request.
> > Reported issue is now resolved - it was related to the hardware component installed in the keyboard (USB) and identified as a cause to the error messages in syslog.
>
> Ok. But perhaps brltty could be less verbose here?
>
> Samuel