user with root access can open it but not normal user
journalctl show this error
Starting at-spi-dbus-bus.service - Accessibility services bus...
fedora systemd[5899]: at-spi-dbus-bus.service: Failed to locate executable /usr/libexec/at-spi-bus-launcher: Permission denied
fedora systemd[5899]: at-spi-dbus-bus.service: Failed at step EXEC spawning /usr/libexec/at-spi-bus-launcher: Permission denied
fedora systemd[3937]: at-spi-dbus-bus.service: Main process exited, code=exited, status=203/EXEC
fedora systemd[3937]: at-spi-dbus-bus.service: Failed with result 'exit-code'.
fedora systemd[3937]: Failed to start at-spi-dbus-bus.service - Accessibility services bus.
fedora systemd[5900]: at-spi-dbus-bus.service: Failed to locate executable /usr/libexec/at-spi-bus-launcher: Permission denied
fedora systemd[5900]: at-spi-dbus-bus.service: Failed at step EXEC spawning /usr/libexec/at-spi-bus-launcher: Permission denied
endless of these…
at-spi-dbus-bus.service: Start request repeated too quickly.
fedora systemd[3937]: at-spi-dbus-bus.service: Failed with result 'exit-code'.
fedora systemd[3937]: Failed to start at-spi-dbus-bus.service - Accessibility services bus.
how to resolve it?
ilikelinux
(Ilikelinux (l.s.))
November 27, 2022, 12:48pm
2
Welcome to ask.fedora @wikabi6531
Please make us a inxi -Fzx
in terminal and post the output here as pre-formatted </>
text.
gnwiii
(George N. White III)
November 27, 2022, 1:19pm
3
You haven’t provided enough information. The request for inxi -Fzx
gives us your OS and some hardware details.
kki hhe:
Permission denied
errors often occur if you have not booted after updating, or after an ill-advised (by Dr. Google) attempt to fix some other problem. When problems like this appear they may disappaer after an update and reboot. If you recently attempted to fix problems with file ownership or access, a bit of the historical background could be helpful.
Can you clarify
Do you mean it works using sudo
or doas
from a regular user login?
It would be useful to compare your system with the following (from aworking Fedora 37 system (...%
is the zsh prompt, for bash you see <something>$
):
...% ls -l /usr/libexec/at-spi-bus-launcher
-rwxr-xr-x. 1 root root 32960 Jul 20 18:33 /usr/libexec/at-spi-bus-launcher
...% file /usr/libexec/at-spi-bus-launcher
/usr/libexec/at-spi-bus-launcher: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=40dfe855706e15f70f03186db6bd98eac6b25580, for GNU/Linux 3.2.0, stripped
...% ldd /usr/libexec/at-spi-bus-launcher
linux-vdso.so.1 (0x00007ffcdc1eb000)
libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007fa014892000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007fa014831000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fa0146f1000)
libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007fa014614000)
libX11.so.6 => /lib64/libX11.so.6 (0x00007fa0144cd000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa0142f1000)
libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007fa0142e8000)
libz.so.1 => /lib64/libz.so.1 (0x00007fa0142ce000)
libmount.so.1 => /lib64/libmount.so.1 (0x00007fa014287000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fa01425a000)
libffi.so.8 => /lib64/libffi.so.8 (0x00007fa01424e000)
libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007fa0141b1000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007fa0141a5000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fa01417a000)
libzstd.so.1 => /lib64/libzstd.so.1 (0x00007fa0140c7000)
liblz4.so.1 => /lib64/liblz4.so.1 (0x00007fa0140a3000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa014083000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa014a92000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007fa014058000)
libblkid.so.1 => /lib64/libblkid.so.1 (0x00007fa01401d000)
libXau.so.6 => /lib64/libXau.so.6 (0x00007fa014017000)