Bug#911362: few packages report not able to register with accessibility bus

[Samuel Thibault]

Hello,

shirish शिरीष, le ven. 19 oct. 2018 11:35:52 +0530, a ecrit:
> I am not sure who or which package is at fault here but the last time
> it was reported against at-spi2-core #732618 so guess that is a good
> starting place.

Yes, that's probably where the issue is.

> I did see this however
> 
> $ xprop -root | grep SPI
> AT_SPI_BUS(STRING) =
> "unix:abstract=/tmp/dbus-BDMhmQ5eOi,guid=30a45fa7981ed0af656dc4ea5bc90e54"
> shirish at debian:~$ dbus-monitor --address
> unix:abstract=/tmp/dbus-BDMhmQ5eOi,guid=30a45fa7981ed0af656dc4ea5bc90e54
> Failed to register connection to bus at
> unix:abstract=/tmp/dbus-BDMhmQ5eOi,guid=30a45fa7981ed0af656dc4ea5bc90e54:
> 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.

Ok, so the issue is that the accessibility bus somehow died. Do you
have a reproducer? Is there an at-spi-bus-launcher process and the
corresponding dbus-daemon process?  Perhaps dmesg can also tell in case
it died with e.g. a segfault?

> from https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/

Good thing that I wrote that page, it seems to have been useful here :)

Samuel