Sebastien Bacher, le ven. 13 sept. 2019 10:30:10 +0200, a ecrit: > I'm able to reproduce by starting the test manually on a canonistack > instance > > $ xvfb-run -a dbus-run-session gdb ./atk-test > ... > [Detaching after fork from child process 10080] > child_pid 10080 > 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 Samuel
