When attempting to start evolution (version mail-client/evolution-3.46.3-r1), the mail client attempts to start and then quits with the message: evolution:3204): dbind-WARNING **: 13:38:20.811: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied (evolution-alarm-notify:3211): dbind-WARNING **: 13:38:21.024: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied bwrap: Can't find source path /root/.cache/at-spi: Permission denied When setting /root and /root/.cache/at-spi to a=xwr (which I obviously don't want to for long), then evolution starts. The behavior appears in kernel 4.19.277-gentoo and 6.1.19-gentoo
Are you attempting to run evolution as root?
No, I run evolution as a standard user, not as root. I tried it also with another user account, same thing. I have no idea why evolution wants to store data under /root/.cache/at-spi
Is XDG_CACHE_HOME set in the environment?
XDG_CACHE_HOME has not been set. It also isn't in my older gentoo machines where evolution is running. I tried to set XDG_CACHE_HOME to /home/username/.cache but it did not help either.
I want to share that I'm seeing the same error with `inkscape`: ``` $ inkscape --export-background-opacity=0 --export-width=2999 --export-type=png --export-filename=aiohttp-old-logo.png old-logo.svg (inkscape:1276735): dbind-WARNING **: 17:00:35.277: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied ``` It does not crash, doing its job successfully (image conversion). But I think I've seen similar messages from other programs. I'm not running it as root, and it's not clear where the root home dir is coming from and the obvious vars are empty: ``` $ echo $HOME /home/<username> $ echo $XDG_CACHE_HOME $ echo $AT_SPI_BUS_ADDRESS $ env | grep /root $ gdbus call --session --dest org.a11y.Bus --object-path /org/a11y/bus --method org.a11y.Bus.GetAddress ('unix:path=/run/user/1000/at-spi/bus_0,guid=d19ee2620e74667254a461ae66a117ca',) ``` This suggests that the problem might be that either some apps invoke `sudo` internally (though, why would they?) or perhaps the problem is somewhere on the gtk/dbus level.. I'm not really familiar with these, so it's just a speculation that keeps me puzzled.
Interestingly, sticking `strace` in front of the command doesn't output that warning and makes it access the proper socket path: ``` connect(9, {sa_family=AF_UNIX, sun_path="/run/user/1000/at-spi/bus_0"}, 29) = 0 ```
Weird… Now, running the same command without `strace` in the same terminal session does not emit said warning. Without any changes whatsoever. So it might be happening unpredictably, then.
