Arch Linux

ball

Member

From: Germany

Registered: 2011-12-23

Posts: 164

[SOLVED] How to control at-spi2-registryd and spi-bus-launcher?

Hello,

I just skimmed the output of htop and discovered two, to my impression, strange processes, of which I never heard before and whose importance to my system is dubious: at-spi2-registryd and at-spi-bus-launcher. See the output of ps aux:

freddy    1222  0.0  0.0 335408  7236 ?        Sl   11:16   0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
freddy    1229  0.0  0.0 123156  6176 ?        Sl   11:16   0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session

These processes are launched by init and apparantly have something to do with accessiblity and gtk3 -- but this is pretty much all I could find out about them.

May I disable these processes? And if yes, how? I grep'd the output of systemctl but I couldn't find any clues on how to prevent them being launched on system startup. The fact that gtk3 requires the packages which provide the offending files prevents me from removing them from my system.

I neither use gnome (which may be indicated by the output above), nor do I use a display manager: I log in straight into X and start dwm.

Last edited by ball (2014-11-17 22:19:00)

jjacky

Member

Registered: 2011-11-09

Posts: 347

Website

Re: [SOLVED] How to control at-spi2-registryd and spi-bus-launcher?

As I said in a recent task, those are indeed launched as a result of running GTK3 apps, but if you have NO_AT_BRIDGE=1 set in your environment then it should prevent them for being started.

---

blog - github

ball

Member

From: Germany

Registered: 2011-12-23

Posts: 164

Re: [SOLVED] How to control at-spi2-registryd and spi-bus-launcher?

Thanks, this is solved.  However the default behaviour is quite irritating...

AnAkkk

Member

Registered: 2014-03-03

Posts: 148

Re: [SOLVED] How to control at-spi2-registryd and spi-bus-launcher?

Unfortunately, even with NO_AT_BRIDGE=1 at-spi-bus-launcher is still launched as soon as I launch firefox.

ball

Member

From: Germany

Registered: 2011-12-23

Posts: 164

Re: [SOLVED] How to control at-spi2-registryd and spi-bus-launcher?

@AnAkkk: True.  This is quite annoying. Did anyone already file a bug upstream? If not: where would one have to report this issue: at gtk or gnome development?

Edit: I've just recognized that both projects use the same bugtracker: http://bugs.gnome.org

Last edited by ball (2014-11-18 21:00:17)

serdotlinecho

Member

Registered: 2013-01-26

Posts: 100

Re: [SOLVED] How to control at-spi2-registryd and spi-bus-launcher?

Unfortunately, even with NO_AT_BRIDGE=1 at-spi-bus-launcher is still launched as soon as I launch firefox.

Try add this in pacman.conf:

NoExtract = usr/share/dbus-1/services/org.a11y.*

Reinstall gtk3 and at-spi2-core:

sudo pacman -S gtk3 at-spi2-core

Logout and login back. I hope it works!

Last edited by serdotlinecho (2014-11-24 14:55:24)

st1vms

Member

Registered: 2022-11-07

Posts: 1

Re: [SOLVED] How to control at-spi2-registryd and spi-bus-launcher?

The suggested answers didn't actualy prevent the at-spi process to be restarted across reboots.

By linking at-spi services and config files to /dev/null (after performing a backup), the block was persistent across reboots, without actually breaking the system.
 
This script does both, in case anyone needs ...

#!/usr/bin/bash

# This script requires sudo privileges in order to work!
#
# It links at-spi2 dbus services and config files to /dev/null after performing a backup.

# Backup directory, it'll be created if non-existent
BACKUP_DIR="$HOME/at-spi2-bak"

# service and config files directories
DIR_S="/usr/share/dbus-1/services"
DIR_AS="/usr/share/dbus-1/accessibility-services"
DIR_DC="/usr/share/defaults/at-spi2"

# List of files to nullify (single line)

FILES_LINE="$DIR_S/org.a11y.Bus.service \
$DIR_AS/org.a11y.atspi.Registry.service \
$DIR_DC/accessibility.conf \
"\

# Ensures backup folder exists
mkdir -p "$BACKUP_DIR"

echo "Performing backup..."

for f in $FILES_LINE
do
    rsync -av "$f" "$BACKUP_DIR/"
done

# Link to /dev/null at-spi bus files
echo "Linking files to /dev/null ..."

for f in $FILES_TOUNLINK
do
    ln -fs /dev/null "$f"
done

echo "done."