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

[Samuel Thibault]

Hello,

charles xavier, le lun. 26 août 2019 03:47:50 +0200, a ecrit:
> my system seems to have found a way.

Ok, good, so we can check what is happening :)

How do you run your X session? Through a DM like lightdm (which one?) or
through startx or something else?

> Other GTK apps (e.g. gimp, ristretto, xournal) report a different message that may be related:
> Gtk-Message: 12:34:56.789: Failed to load module "atk-bridge"

That one is easy: that is because libatk-adaptor is not installed.

> Please find below various system info. Note the tmp filenames, userid, and guids have been changed to bogus but consistent values.

Ok, thanks!

> % ps aux|grep -i at-spi|grep -v grep
> xavier     895  0.0  0.0 312472  5172 ?        Ssl  Jul20   0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
> xavier     917  0.0  0.0   8968  3144 ?        S    Jul20   0:53 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
> xavier    8546  0.0  0.0 174108  5908 ?        Sl   Jul20   3:07 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
> root     30144  0.0  0.0 312460  5632 ?        Sl   Jul20   0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
> root     30149  0.0  0.0   8840  2912 ?        S    Jul20   0:42 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
> root     30151  0.0  0.0 174148  6012 ?        Sl   Jul20   3:03 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session

So at-spi2 is definitely running (which is expected, it's started from
/etc/xdg/autostart/at-spi-dbus-bus.desktop)

> % xprop -root | grep SPI
> AT_SPI_BUS(STRING) = "unix:abstract=/tmp/dbus-0XXXXXXXXX,guid=0000000000000000123456789abcdef0"
> % dbus-monitor --address "unix:abstract=/tmp/dbus-0XXXXXXXXX,guid=0000000000000000123456789abcdef0"
> Failed to register connection to bus at unix:abstract=/tmp/dbus-0XXXXXXXXX,guid=0000000000000000123456789abcdef0: 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.

Could you also try to connect to the bus reported in

> PASS: got accessibility bus unix:abstract=/tmp/dbus-3XXXXXXXXX,guid=3333333333333333123456789abcdef0 from session dbus

?

> FAIL: mismatch between $DBUS_SESSION_BUS_ADDRESS (unix:path=/run/user/31337/bus) and well-known path /home/xavier/.dbus/session-bus/1111111111111111123456789abcdef0-0 (unix:abstract=/tmp/dbus-2XXXXXXXXX,guid=2222222222222222123456789abcdef0)

This mismatch shouldn't harm, but how old is
/home/xavier/.dbus/session-bus/1111111111111111123456789abcdef0-0?

Samuel