Skip to main content ↑ ↓
Topic: [SOLVED] at-spi mystery (Read 1529 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] at-spi mystery

I run a test vm based on lxqt-runit-20250407; when I ssh to it I can run gvim via X11forwarding in the normal way. Running in an
ssh terminal I see no messages as gvim is started.

To use gvim as root I transfer the .Xauthority via
 
Code: [Select]
$ sudo su
# rm -f /root/.Xauthority
# xauth add $(xauth -f ~robin/.Xauthority list|tail -1)
# gvim 

(gvim:966): dbind-WARNING **: 10:28:26.661: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/busartix-runit_10.0: No such file or directory
gvim works, but where does the at-spi message come from. I don't see that when running as robin. Does root need some additional setup? Do I have to transfer access to some bus? This command also gives the message
Code: [Select]
# sudo -u robin gvim

(gvim:1497): dbind-WARNING **: .......

Whre does at-spi get involved. I see no daemon running with ati involvement (I see it with sddm running).

If I run sudo gvim  in an X11 terminal emulator I don't see the warning.

Re: at-spi mystery

Reply #1 –
Seems this is something artificially foisted on the unsuspecting by gnome GTK3/4 apps (maybe gtk2 as well).

Apparently most modern gtk applications start up at accessibility stuff on a special dbus. I tried various ways of disabling, but all failed except the use of export NO_AT_BUS=1. I'm not sure why this isn't needed in the case of my normal user, but probably bus ownership is involved.

I put export NO_AT_BUS=1 into my .profile and then force it into the sudoers file with sudo visudo by adding a line
Code: [Select]
Defaults env_keep += "NO_AT_BRIDGE"

Re: [SOLVED] at-spi mystery

Reply #3 –
Thanks for the pointer, I must have missed this thread. Not sure why the gnomians couldn't have put in a central config somewhere to turn this sort of thing off. Perhaps they have, but it's too hard to find :(

Re: [SOLVED] at-spi mystery

Reply #4 –
Quote from: replabrobin – on
Thanks for the pointer, I must have missed this thread. Not sure why the gnomians couldn't have put in a central config somewhere to turn this sort of thing off. Perhaps they have, but it's too hard to find :(
It's not possible, they despise users having control over their stuff so they go out of their way to restrict certain shit, don't give them that benefit of the doubt...
Here's the most egregious example of calling out Arch users and mocking them as clowns...
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4829