Bug#728385: libatspi2.0-0: warning "Couldn't connect to accessibility bus"
On 2013-11-01 01:15:56 +0100, Samuel Thibault wrote:
> Vincent Lefevre, le Thu 31 Oct 2013 16:32:19 +0100, a écrit :
> > When I run a program like Emacs or gnome-terminal, I get a warning
> > like:
> >
> > ** (emacs:8308): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-jdE6OWQwEd: Connection refused
> > ** (gnome-terminal:8770): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-jdE6OWQwEd: Connection refused
> >
> > This doesn't seem to occur normally (unless something has changed),
> > but currently I get this when running the application via SSH with
> > X forwarding.
>
> Yes, this is actually "expected": proper accessibility forwarding
> through SSH does not exist yet AFAIK.
This isn't true (or there is another bug): I didn't get the warning
after a "ssh -Y":
ypig:~> ssh -Y xvii
[...]
xvii:~> emacs
xvii:~> emacs
xvii:~> gnome-terminal
xvii:~>
But this worked only once.
Currently I also get the warning on my local machine ypig!
On 2013-11-01 01:26:58 +0100, Vincent Lefevre wrote:
> On 2013-11-01 01:15:56 +0100, Samuel Thibault wrote:
> > So in the end I'm afraid this warning will just keep showing up until
> > somebody properly implements accessibility forwarding through SSH.
>
> I don't mind about accessibility, and this warning is more annoying
> than informative. The libatspi library should provide a way to hide
> it, at least when the application is run via SSH.
Setting NO_AT_BRIDGE=1 as found on
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15154
avoids accessibility, thus the warning as well.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: