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

Samuel Thibault sthibault at debian.org
Fri Sep 13 09:44:45 BST 2019

Samuel Thibault, le ven. 13 sept. 2019 10:37:23 +0200, a ecrit:
> Sebastien Bacher, le ven. 13 sept. 2019 10:30:10 +0200, a ecrit:
> > dbus-daemon[10074]: [session uid=1000 pid=10074] Activating service
> > name='org.a11y.Bus' requested by ':1.0' (uid=1000 pid=10077
> So it's apparently the right dbus-daemon which starts the at-spi service.
> > ** (at-spi2-registryd:10093): WARNING **: 08:24:49.049: AT-SPI: Cannot
> > open default display
> But for some reason XOpenDisplay(NULL) failed to connect to the Xvfb
> started by xvfb-run, and all the rest comes from this. Do you have xauth
> installed and does xvfb-run properly set things for X applications to
> connect? You might want to check with
> $ xvfb-run -a /usr/bin/xlogo

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


More information about the Pkg-a11y-devel mailing list