Still happening in May 2022 on xubuntu 22.04 with xfce
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed to connect
Comment #20 appears to recommend filing a deliberate duplicate:
> Please open your own report if you are affected.
One such duplicate is Bug #1617630.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
Still present running meld on Xubuntu 16.04.2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed to connect to socket
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
I got this error on 14.04 when opening Emacs and Gedit from the
terminal. The NO_AT_BRIDGE worked for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to
Please open your own report if you are affected.
** Changed in: gnome-session (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
seen in 15.04 running Cheese.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed to connect to socket
/tmp/dbus-*
This is no more an issue on my system (but cant tell why)
** Changed in: at-spi2-core (Ubuntu)
Status: Confirmed => Invalid
** Changed in: at-spi2-core (Debian)
Importance: Unknown => Undecided
** Changed in: at-spi2-core (Debian)
Status: Confirmed => New
** Changed in:
** Tags removed: saucy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed to connect to socket
/tmp/dbus-*
Status in
Fresh install 14.04.02. export NO_AT_BRIDGE=1 works as a workaround.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed
** Bug watch removed: GNOME Bug Tracker #695228
https://bugzilla.gnome.org/show_bug.cgi?id=695228
** Bug watch removed: Debian Bug tracker #702517
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517
--
You received this bug notification because you are a member of Desktop
Packages,
Triggered by baobab on Ubuntu 14.04. If I add the following to my
.bashrc, the message stops appearing:
export NO_AT_BRIDGE=1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
If I add the following to my .bashrc, the message stops appearing:
export NO_AT_BRIDGE=1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to
Problem still visible in Xubuntu 14.10, for all Gtk applications.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed to
same on Ubuntu 14.04.1 when runing light-locker.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed to connect to
I am getting the error on fresh installation of lubuntu 14.10 amd64 when
I try to use zenity.
** Tags added: utopic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
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
Affects Xubuntu 14.10 amd64 when launching ubuntu-tweak.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus: Failed to connect
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
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:
** Changed in: at-spi2-core (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility
** This bug is no longer a duplicate of bug 1347272
Several XFCE applications appear unresponsive after communicating with a
daemon
** Package changed: gdk-pixbuf (Ubuntu) = at-spi2-core (Ubuntu)
** Bug watch added: GNOME Bug Tracker #711359
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/msg6.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: at-spi
Status: Unknown = New
** Changed in: at-spi
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't
** Changed in: at-spi2-core (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
Couldn't connect to accessibility bus:
*** This bug is a duplicate of bug 1347272 ***
https://bugs.launchpad.net/bugs/1347272
** This bug has been marked a duplicate of bug 1347272
XFCE applications appear irresponsible after communicating with a daemon
--
You received this bug notification because you are a member of Desktop
@ 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
Thanks Alberto! OK, I've submitted a new bug report against dbus:
Bug #1347272 (DBus communication problems affecting multiple packages)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdk-pixbuf in Ubuntu.
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
30 matches
Mail list logo