Remove AT-SPI: Error message

[blur13Member]

at-spi-bus-launcher enables accessibility technologies such as screen readers. If you dont need it:

sudo apt remove at-spi2-core

this will cause all sorts of applications to generate the following error:

AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

This can safely be ignored, but it can be a bit annoying. To disable:

in .bashrc add
export NO_AT_BRIDGE=1

This has been documented and suggested before, however, this will not suppress the warnings when running commands as sudo. So, for example, the error will be generated whenever the standard update command “sudo apt update && sudo apt dist-upgrade -V” is run and desktop-menu is triggered by apt hook.

In order to remove the warnings for the sudo user, edit (as root/sudo)
/etc/sudoers.d/antixers

at the very end, add:
Defaults env_keep += "NO_AT_BRIDGE"

Problem solved.

[PPCMember]

Thanks for this new tip. By the way are there any noticeable saving in resource usage, removing this package? Or you do it just to have a leaner system?

P.

[blur13Member]

Here is a fairly recent issue

http://forums.freebsd.org/threads/at-spi-bus-launcher-eats-all-the-memory.89570/

The more things you’ve got running, the more things could potentially go wrong. There is no reason to enable a daemon that runs 24/7 if it doesnt have a purpose.

In this case, the “savings” in terms of RAM are not noticeable, maybe less than 3 MiB. Not sure about CPU usage.

But if you start trimming services you dont need (CUPS, ssh, bluetooth, pipewire, connman, ntpd) it adds up.

In this case I think the annoyance came from disabling a service and it spams the logs with error messages that aren’t really errors.

[m4r35n357Member]

I have been attempting to disable that “service” again recently. The solution:

export NO_AT_BRIDGE=1

used to work, but not any more. Those lovely folks at freedesktop/ibm/redhat/gnome have restored the “functionality” of this “service” so it gets started by pretty much anything that uses gtk. I have come up with something that works:

sudo chmod -x /usr/libexec/at-spi*

but of course the warnings come back. IMO they are now a feature.

I expect my changes to be reverted if gtk or whatever gets updated, so I will eventually have to consider making them immutable too, which might cause even more problems at update time.

Bah!!!!

[olsztynMember]

m4r35n357 wrote:

have come up with something that works:

sudo chmod -x /usr/libexec/at-spi*

but of course the warnings come back. IMO they are now a feature.

I have been running with removed at-spi-core for a long time with no adverse effect except those messages.
However I will try your solution, for which I will need to reinstall it.
This at-spi gtk virus has been annoying but I learned to ignore those messages over time.

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[m4r35n357Member]

I noticed the trojan had reappeared on my Raspberry Pis – I let my guard down (what is it they say about “eternal vigilance”?). One of them only has FVWM/Slim so it stood out among a mere 35 processes (after a fresh login). I only made the latest change today so hoping there are no unforeseen consequences!

[anti-apXosMember]

NO_AT_BRIDGE=1 does not prevent at-spi2-launcher/registry from running, it just prevents GTK apps from spitting out the error message if at-spi2-core isn’t installed.

Note that on antix you can purge at-spi2-core without touching at-spi2-common, so that nothing else gets dragged out with it. I believe this little trick is due to the kind ministrations of anticapitalista.

"--"

[m4r35n357Member]

OK that sounds like a better solution, thanks!

[Author]

Posts