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

Samuel Thibault samuel.thibault at ens-lyon.org
Fri Aug 23 20:34:44 BST 2019


DM, le ven. 23 août 2019 19:00:40 +0000, a ecrit:
> 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?

I guess that's simply because this device has the same ID as some of
the generic IDs that happen to be used for braille devices, and which
we thus want to detect as braille devices and trigger accessibility

Still, there is no reason why brltty should be spamming the logs in such
a case.


More information about the Pkg-a11y-devel mailing list