On Sat, Apr 19, 2014 at 05:52:53PM +0100, Patrick Welche wrote:
> I have been upgrading eg dbus, glib, at-spi2-core etc. and now registryd
> won't start. The best test so far, which is I think what
> get_accessibility_bus_address_dbus() does in at-spi2-core atspi-misc.c is:
>
> dbus-send --print-reply --dest=org.a11y.Bus /org/a11y/bus \
> org.a11y.Bus.GetAddress
>
> which returns:
>
> Error org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.a11y.Bus
> exited with status 1
>
> This suggests that the session bus is running sufficiently to accept a
> connection, but then something fails - any clues on how to find out what?
Possible clue from at-spi2-core/registryd/testregistry.py?
$ python3.3 testregistry.py
File "testregistry.py", line 38
print apps
^
SyntaxError: invalid syntax
$ python2.7 testregistry.py
Traceback (most recent call last):
File "testregistry.py", line 59, in <module>
sys.exit(main(sys.argv))
File "testregistry.py", line 48, in main
introspect=False)
File "/usr/pkg/lib/python2.7/site-packages/dbus/bus.py", line 241, in
get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/pkg/lib/python2.7/site-packages/dbus/proxies.py", line 248, in
__init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/pkg/lib/python2.7/site-packages/dbus/bus.py", line 180, in
activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/pkg/lib/python2.7/site-packages/dbus/bus.py", line 278, in
start_service_by_name
'su', (bus_name, flags)))
File "/usr/pkg/lib/python2.7/site-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited:
Process org.a11y.Bus exited with status 1
Cheers,
Patrick
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
