Bug#940018: at-spi2-atk autopkgtest fail most of the time on s390x

Samuel Thibault sthibault at debian.org
Fri Sep 13 10:02:59 BST 2019

Sebastien Bacher, le ven. 13 sept. 2019 10:54:07 +0200, a ecrit:
> Le 13/09/2019 à 10:44, Samuel Thibault a écrit :
> > Just thinking: is that dbus-daemon which is the parent of
> > at-spi2-registryd (and thus gives it its environment variables)?  I
> > vaguely remember "systemd --user" taking over that role, but possibly it
> > misses passing the DISPLAY variable along?...
> Yes xauth is installed and e.g xlogo works.

Ok, so that must be something with the dbus activation.

Perhaps you could replace /usr/lib/at-spi2-core/at-spi2-registryd with a
script which dumps the output of ps axuf and printenv to a file, so we
get to be sure in which situation it gets started.

> If it was a problem with the way dbus is set it would probably not be
> arch specific?

Normally it wouldn't. "Normally".

> I've tried to ssh -X (which success to start xlogo locally over ssh) and
> $ dbus-run-session ./atk-test
> # random seed: R02Se0d960b12c7b7375a48b46c8448ee3fb
> 1..158
> # Start of Accessible tests
> run_app:
> /home/ubuntu/build/at-spi2-atk-2.34.0/tests/data/test-accessible.xml
> child_pid 11208
> Bail out! dbind-FATAL-ERROR: AT-SPI: Couldn't connect to accessibility
> bus. Is at-spi-bus-launcher running?

Unfortunately at-spi can't work remotely like this, it has to be a local
X session, ssh X forwarding is not enough.


More information about the Pkg-a11y-devel mailing list