Re: [g-a-devel] "Couldn't register with accessibility bus" Error
- From: Mike Gorse <mgorse alum wpi edu>
- To: Nischal Rao <rao nischal gmail com>
- Cc: gnome-accessibility-devel gnome org
- Subject: Re: [g-a-devel] "Couldn't register with accessibility bus" Error
- Date: Thu, 9 Jun 2011 14:09:16 -0400 (EDT)
Thanks for the report. I believe this is fixed in at-spi2-core master
(the fix I committed works for me, anyway, and I've filed / attached it to
BGO#652215). I also submitted a request to have the patch added to the
OpenSUSE package in GNOME:STABLE:3.0.
On Sun, 5 Jun 2011, Nischal Rao wrote:
I sometimes come across the following error in at-spi2 when I try to start an application of mine that uses pyatspi2 :
WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message
bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
process 12330: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
I am able to consistently reproduce this issue by going to the package manager in OpenSUSE (looks like the massive tree structure in the package manager is causing this
error) and then start my application. I also found that applications like Accerciser don't start at all after this (even if I close the package manager application).
Nischal E Rao
Download VEDICS @ http://vedics.sourceforge.net/
] [Thread Prev