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

shirish शिरीष shirishag75 at gmail.com
Sat Oct 20 14:48:50 BST 2018


Reply in-line :-

On 20/10/2018, Samuel Thibault <sthibault at debian.org> wrote:
> Hello,
>

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?
>

I don't have the bug anymore. Either due to some of the updates in-between
today and yesterday the bug either got fixed or covered.

I got good feedback from ally now though I am not sure if there are any
security considerations if sharing the output of dbus-monitor

This time it does check for mouse events and listens to them .

I can share it privately if needed.

I did look at dmesg but nothing jumped at me.

>> from https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/
>
> Good thing that I wrote that page, it seems to have been useful here :)
>

It was, a small minor improvement though perhaps -

instead of

 git clone git://git.debian.org/git/pkg-a11y/check-a11y

please put -

 git clone https://git.debian.org/git/pkg-a11y/check-a11y

Maybe we could have that script packaged, possibility ?

I did run the troubleshooting script and found the following though -

~/games/check-a11y$ ./troubleshoot
Packages
PASS: at-spi2-core installed
PASS: libgail-common installed
PASS: libatk-adaptor installed
PASS: qt-at-spi installed
PASS: libatk-wrapper-java installed

Running environment
PASS: at-spi-bus-launcher is running as user shirish
PASS: at-spi2-registryd is running as user shirish
PASS: got accessibility bus
unix:abstract=/tmp/dbus-rc2Mhin7Pp,guid=ba8fffe5e73231fe9b67e6055bcac698
from session dbus
PASS: got accessibility bus
unix:abstract=/tmp/dbus-rc2Mhin7Pp,guid=ba8fffe5e73231fe9b67e6055bcac698
from root window
PASS: accessibility buses from session dbus and from root window match

Layer enabling
WARN: screen-reader-enabled not set to true in
org.gnome.desktop.a11y.applications gsettings, and
QT_LINUX_ACCESSIBILITY_ALWAYS_ON is not set to 1, Qt5 applications may
not be accessible
WARN: assistive technology not enabled in
/etc/java-8-openjdk/accessibility.properties, Java 8 Swing
applications may not be accessible.
WARN: default Look and Feel is not GTK in
/etc/java-8-openjdk/swing.properties, Java 8 Swing applications may
not be accessible.
PASS: assistive technology enabled in
/etc/java-10-openjdk/accessibility.properties.
WARN: default Look and Feel is not GTK in
/etc/java-10-openjdk/swing.properties, Java 10 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.

It also doesn't tell why the default look and feel for java-11 is not GTK

:/etc/java-11-openjdk$ cat accessibility.properties
#
# The following line specifies the assistive technology classes
# that should be loaded into the Java VM when the AWT is initailized.
# Specify multiple classes by separating them with commas.
# Note: the line below cannot end the file (there must be at
# a minimum a blank line following it).
#
# Doesn't work, see LP: #935296
#assistive_technologies=org.GNOME.Accessibility.AtkWrapper

I couldn't find #935296 in launchpad :(

> Samuel
>

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8



More information about the Pkg-a11y-devel mailing list