Arch Linux

bwv549

Member

Registered: 2013-12-13

Posts: 14

[SOLVED] "Couldn't register with accessibility bus: Did not receive...

When I start up a gtk based application (tested on gedit and evince) I get this kind of warning message:

** (evince:9781): 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.

I don't get this kind of message when starting something like chromium or gvim.  KDE apps give me distinct dbus messages, mainly upset that the QT apps weren't started before dbus.

Here are the values from the relevant env variables:

 $ echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-hZkItzPOw3,guid=5215dcfecdaa4eeaa577ac2952efd716
$ echo $DBUS_SESSION_BUS_PID 

### [^gives no output]

My dbus service appears to be running:

$ systemctl status dbus.service                                                            
dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
   Active: active (running) since Mon 2014-02-03 10:51:06 MST; 30min ago
 Main PID: 221 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─221 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Feb 03 10:51:07 prince dbus[221]: [system] Activating via systemd: service name='org.freedesktop.ColorManager'...rvice'
Feb 03 10:51:08 prince dbus[221]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Feb 03 10:51:10 prince dbus[221]: [system] Activating via systemd: service name='org.freedesktop.Accounts' uni...rvice'
Feb 03 10:51:10 prince dbus[221]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' u...rvice'
Feb 03 10:51:10 prince dbus[221]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 03 10:51:10 prince dbus[221]: [system] Successfully activated service 'org.freedesktop.Accounts'
Feb 03 10:51:18 prince dbus[221]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1'...rvice'
Feb 03 10:51:18 prince dbus[221]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 03 11:13:41 prince dbus[221]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit...rvice'
Feb 03 11:13:41 prince dbus[221]: [system] Successfully activated service 'org.freedesktop.UDisks2'

I'm running i3 and lightdm as display manager.

Last edited by bwv549 (2014-07-25 21:27:45)

bwv549

Member

Registered: 2013-12-13

Posts: 14

Re: [SOLVED] "Couldn't register with accessibility bus: Did not receive...

May be related to Ubuntu bug 1222356, for which no solution has yet been posted as of Feb 17, 2014.

orschiro

Member

Registered: 2009-06-04

Posts: 2,136

Website

Re: [SOLVED] "Couldn't register with accessibility bus: Did not receive...

Same for me here for GTK3 applications.

birdie 

** (birdie:16603): 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.

Do you notice anything to be not working? At least not me.

Last edited by orschiro (2014-02-26 06:21:43)

---

@orschiro

bwv549

Member

Registered: 2013-12-13

Posts: 14

Re: [SOLVED] "Couldn't register with accessibility bus: Did not receive...

No, everything seems to be functional; I'm just annoyed with the extra noise.  If it is registering with dbus, then the application shouldn't be saying it is not registering.  If it is indeed not registering, then perhaps certain features are broken, and I just don't realize it.

However, your question, orschiro, indeed serves to emphasize the point: this is a low priority issue, as far as we can tell.

karl.drago

Member

Registered: 2014-07-20

Posts: 1

Re: [SOLVED] "Couldn't register with accessibility bus: Did not receive...

According to https://wiki.archlinux.de/title/GNOME#Tipps_und_Tricks, this warning can be put off by setting

export NO_AT_BRIDGE=1

in /etc/environment.

bwv549

Member

Registered: 2013-12-13

Posts: 14

Re: [SOLVED] "Couldn't register with accessibility bus: Did not receive...

Awesome, thank you!!  I went ahead and put the setting in ~/.profile since I'm not yet convinced that it is a system-wide problem (e.g., does this bug affect gnome users too?).  Marking as solved.

jakub

Member

Registered: 2013-09-14

Posts: 151

Re: [SOLVED] "Couldn't register with accessibility bus: Did not receive...

I'm encountering something similar since since updating gnome to 3.14

[kuba@t61 ~]$ nautilus

** (nautilus:1727): 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.
[kuba@t61 ~]$ 

[kuba@t61 ~]$ systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
   Active: active (running) since czw 2014-10-16 18:51:43 CEST; 23min ago
     Docs: man:dbus-daemon(1)
 Main PID: 243 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─243 /usr/bin/dbus-daemon --system --address=systemd: --nofork --...

[kuba@t61 ~]$ echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-IEuJ4ENh4e,guid=445f2ed38552aa1aaf9d7dc3543ff82e
[kuba@t61 ~]$ echo $DBUS_SESSION_BUS_PID 

[kuba@t61 ~]$ 

Last edited by jakub (2014-10-16 17:17:41)