a11y bus debugging

Patrick Welche prlw1 at cam.ac.uk
Thu Aug 21 15:49:24 PDT 2014


I am trying to work out why

$ ./at-spi-bus-launcher --launch-immediately
Failed to launch bus: Failed to connect to session bus

given

 1006 ?      Is   0:00.00 /usr/pkg/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 

and could use some guidance on debugging this...


One problem is that it is only after at-spi-bus-launcher.c:640's

g_main_loop_run (_global_app->loop);

that I see an error:

(gdb) print *_global_app
$15 = {loop = 0x7f7ff772d620, launch_immediately = 1, a11y_enabled = 0, 
  screen_reader_enabled = 0, session_bus = 0x0, a11y_schema = 0x7f7ff771edc0, 
  interface_schema = 0x7f7ff771ec80, state = A11Y_BUS_STATE_IDLE, 
  a11y_bus_pid = 0, a11y_bus_address = 0x0, pipefd = {0, 0}, 
  a11y_launch_error_message = 0x7f7ff77031d0 "Failed to connect to session bus"}

so I don't really know where to look for the actual failure.

I assume that the session bus is alright as:

get_uninitialized_connection(bus_type=G_BUS_TYPE_SESSION,...) succeeds.

but then, why the subsequent failure?


Cheers,

Patrick


More information about the dbus mailing list