Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*

Status changed to 'Confirmed' because the bug affects multiple users.

I still get this error in Xubuntu 14.04 when I run "sudo gnome-disks", and possibly other commands that I can't recall at the moment:

$ sudo gnome-disks
[sudo] password for mspacek:

** (gnome-disks:474): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-xW1zTsGFKW: Connection refused

Bug #1314782 suggests there's a dbus race condition affecting lots of packages in Ubuntu.

@ Martin Spacek:

I have just triaged the bugs you mentioned.

Please do the following:

 1. Being in Xubuntu 14.04, into the Terminal, enter "ubuntu-bug dbus" and follow steps for reporting this same bug for the Trusty release.

 2. Mention the bug number you just reported in every related report you know, including this.

Then I will triage your report as critical and report it to the XFCE developers.

Thanks Alberto! OK, I've submitted a new bug report against dbus:

Bug #1347272 (DBus communication problems affecting multiple packages)

This mailing list entry explains why a warning message may appear when an application is run as root:

https://mail.gnome.org/archives/gnome-accessibility-devel/2011-June/msg00006.html

I would like to also confir this bug in a 14.04.1 system. I would live to report this using apport-bug but it is that very command that is failing! Here is the terminal output seen when attempting to run this commad:

------------------------------------------------------------------------------------
3-> apport-bug smbclient

** (apport-gtk:7235): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-J9CVMJHXEs: Connection refused
4->
(process:7727): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
------------------------------------------------------------------------------------

After answering various question and getting to the place where it is supposed to write the html file, the browser reports that the file is unavailable (i.e., doesn't exist).

I have used apport-bug a couple of times in the past. This just started today. I rebotted the machine and the problem persisted.

Any known workaround would be appreciated.

The error message:
* is reproducible always,
* on trusty
* with zenity, abiword, gitg, gnome-calculator, probably with other or even all gtk3-apps, too. I have tested only a handful and all exhibit this behavior. Zenity is mentioned in bug #1326099 .

For example:

** (zenity:10455): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-isvBHBGV9Q: Connexion refusée

It seems to have no other side effect as the applications work fine. But this noise in stderr causes troubles, for example in cron jobs.

Affects Xubuntu 14.10 amd64 when launching ubuntu-tweak.

Feedback

Since that reported issue, i've made three fresh installations: utopic 32, utopic 64, trusty 32
they all run gnome-shell.

 As a result, the error reported here has not been seen on these installations: one use its own 'home' folder, the 2 others share a /home partition (the same one used when that report has been opened).

So it seems that some config paramaters/symlinks or package/folder rights (on the system itself, not those inside /home) are wrong or left behind after upgrading.

I am getting the error on fresh installation of lubuntu 14.10 amd64 when I try to use zenity.

same on Ubuntu 14.04.1 when runing light-locker.

Problem still visible in Xubuntu 14.10, for all Gtk applications.

If I add the following to my .bashrc, the message stops appearing:

export NO_AT_BRIDGE=1

Triggered by baobab on Ubuntu 14.04. If I add the following to my .bashrc, the message stops appearing:

export NO_AT_BRIDGE=1

Fresh install 14.04.02. export NO_AT_BRIDGE=1 works as a workaround.

This is no more an issue on my system (but cant tell why)

seen in 15.04 running Cheese.

Please open your own report if you are affected.

I got this error on 14.04 when opening Emacs and Gedit from the terminal. The NO_AT_BRIDGE worked for me.

Same for me, 14.04.05 fully updated. Noticed only today, there was no such an issue before (couple of days at least). Showing up with emacs and evince.

Still present running meld on Xubuntu 16.04.2

Comment #20 appears to recommend filing a deliberate duplicate:

> Please open your own report if you are affected.

One such duplicate is Bug #1617630.

Still happening in May 2022 on xubuntu 22.04 with xfce