Bug#911362: few packages report not able to register with accessibility bus
charles xavier
xavierISdUM4kHmRByIvXeDlpftXZ3 at null.net
Mon Aug 26 02:47:50 BST 2019
Since upgrade to buster, I've been seeing the same behavior as reported in this bug. Not sure if it needs a new bug. Decided on replying to existing bug since this one was left unreproducible, but my system seems to have found a way... Running XFCE with "Enable assistive technologies" unchecked in xfce4-accessibility-settings. The same error as in the report happens with reportbug, exo-open, exo-helper, vlc, mousepad, xarchiver, etc.
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"
Please find below various system info. Note the tmp filenames, userid, and guids have been changed to bogus but consistent values.
% lsb_release -da
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
% uname -r
4.19.0-5-amd64
%apt-cache policy at-spi2-core
at-spi2-core:
Installed: 2.30.0-7
Candidate: 2.30.0-7
Version table:
*** 2.30.0-7 500
500 https://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
% 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
% ps aux|grep -i at-spi|grep -v grep
% 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.
%echo $GTK_MODULES
gail:atk-bridge
%echo $OOO_FORCE_DESKTOP
%echo $GNOME_ACCESSIBILITY
%echo $QT_ACCESSIBILITY
1
%echo $QT_LINUX_ACCESSIBILITY_ALWAYS_ON
%echo $NO_AT_BRIDGE
% git clone https://git.debian.org/git/pkg-a11y/check-a11y
...
% cd check-a11y
% ./troubleshoot
Info
INFO: session type 'x11'
INFO: VT '7'
INFO: session desktop 'lightdm-xsession'
INFO: current desktop 'XFCE'
Packages
PASS: at-spi2-core installed
PASS: libgail-common installed
FAIL: libatk-adaptor not installed, GTK2 applications will not be accessible
FAIL: qt-at-spi not installed, Qt4 applications will not be accessible
PASS: libatk-wrapper-java installed
Running environment
PASS: at-spi-bus-launcher is running as user xavier
PASS: at-spi2-registryd is running as user xavier
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)
PASS: got accessibility bus unix:abstract=/tmp/dbus-3XXXXXXXXX,guid=3333333333333333123456789abcdef0 from session dbus
PASS: got accessibility bus unix:abstract=/tmp/dbus-0XXXXXXXXX,guid=0000000000000000123456789abcdef0 from root window
FAIL: accessibility bus unix:abstract=/tmp/dbus-3XXXXXXXXX,guid=3333333333333333123456789abcdef0 from session dbus doesn't match accessibility bus unix:abstract=/tmp/dbus-0XXXXXXXXX,guid=0000000000000000123456789abcdef0 from root window
WARN: org.a11y.Status IsEnabled is 'false', mozilla applications will not be accessible unless GNOME_ACCESSIBILITY is set to 1
Layer enabling
./troubleshoot: line 177: type: gsettings: not found
WARN: GNOME_ACCESSIBILITY is set to '', mozilla applications will not be accessible unless IsEnabled is set to true (as typically set by starting orca, but not accerciser etc.)
PASS: assistive technology enabled in /etc/java-8-openjdk/accessibility.properties.
WARN: default Look and Feel is not GTK in /etc/java-8-openjdk/swing.properties, Java 8 Swing applications may not be accessible.
WARN: assistive technology not enabled in /etc/java-11-openjdk/accessibility.properties, Java 11 Swing applications may not be accessible.
WARN: default Look and Feel is not GTK in /etc/java-11-openjdk/swing.properties, Java 11 Swing applications may not be accessible.
More information about the Pkg-a11y-devel
mailing list