| View previous topic :: View next topic |
| Author |
Message |
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1492
Location: Richmond Hill, Canada
|
 Posted: Sat Feb 08, 2025 1:59 pm Post subject: |
 |
|
| Da51d wrote: | However, if I try to connect as an ordinary unprivileged user:
| Code: | $ nc -U -z /run/user/134/at-spi/bus_0
nc: /run/user/134/at-spi/bus_0: Permission denied |
Why is this being denied on a file with these permissions? |
Which "user" issue the nc command? is it 134? I think the /run/user/134 directory does not allow other go in there for read/write. |
|
| Back to top |
|
 |
sMueggli
Guru
Joined: 03 Sep 2022
Posts: 541
|
| Posted: Sat Feb 08, 2025 2:05 pm Post subject: |
|
|
| Da51d wrote: | | Why is this being denied on a file with these permissions? |
I guess because of the permissions of /run/user/134.
What is the value of $XDG_RUNTIME_DIR? |
|
| Back to top |
|
|
Da51d
n00b
Joined: 27 Mar 2024
Posts: 62
|
| Posted: Sat Feb 08, 2025 2:24 pm Post subject: |
|
|
OK, thanks both...its true /run/user/134 is rwx------ so stricter than the file itself.
And
| Code: | # echo $XDG_RUNTIME_DIR
/run/user/1000 |
(which is me, 1000, the user)
_________________
What can be said at all can be said clearly and what we cannot talk about we must pass over in silence. |
|
| Back to top |
|
|
sMueggli
Guru
Joined: 03 Sep 2022
Posts: 541
|
| Posted: Sat Feb 08, 2025 3:07 pm Post subject: |
|
|
Your XDG_RUNTIME_DIR looks correct.
Does the at-spi bus exist for your user?
| Code: | | ls -l $XDG_RUNTIME_DIR/at-spi |
? |
|
| Back to top |
|
|
Da51d
n00b
Joined: 27 Mar 2024
Posts: 62
|
| Posted: Sat Feb 08, 2025 3:11 pm Post subject: |
|
|
| Quote: | | Does the at-spi bus exist for your user? |
No, it doesn't:
| Code: | # ls -l $XDG_RUNTIME_DIR/at-spi
ls: cannot access '/run/user/1000/at-spi': No such file or directory |
_________________
What can be said at all can be said clearly and what we cannot talk about we must pass over in silence. |
|
| Back to top |
|
|
sMueggli
Guru
Joined: 03 Sep 2022
Posts: 541
|
| Posted: Sat Feb 08, 2025 3:20 pm Post subject: |
|
|
Does it exist after executing (as normal user) | Code: | | /usr/libexec/at-spi-bus-launcher --launch-immediately |
? |
|
| Back to top |
|
|
Da51d
n00b
Joined: 27 Mar 2024
Posts: 62
|
| Posted: Sat Feb 08, 2025 7:22 pm Post subject: |
|
|
Apologies for the delay...
| Quote: | | Does it exist after executing (as normal user) |
No it doesn't
| Code: | $ /usr/libexec/at-spi-bus-launcher --launch-immediately
$ ls -l $XDG_RUNTIME_DIR/at-spi
ls: cannot access '/run/user/1000/at-spi': No such file or directory |
And thanks for your help...
_________________
What can be said at all can be said clearly and what we cannot talk about we must pass over in silence. |
|
| Back to top |
|
|
dumi
n00b
Joined: 17 Mar 2004
Posts: 28
Location: Czech Republic
|
| Posted: Sun Feb 09, 2025 12:17 pm Post subject: |
|
|
look at permissions for directories above.
/run/user/137 and /run/user/134/at-spi i think they have 700 permisions.
_________________
Software is like sex.
It's better when it's free. |
|
| Back to top |
|
|
Da51d
n00b
Joined: 27 Mar 2024
Posts: 62
|
| Posted: Sun Feb 09, 2025 12:55 pm Post subject: |
|
|
Yes that's right (see about 6 comments back rwx------ =700).
I have set an environment variable NO_AT_BRIDGE=1. This stops the xsession errors. It may possibly solve the problem of evolution not working too, but I have uninstalled evolution, so can't check. But this seems more like a workaround than a solution.
_________________
What can be said at all can be said clearly and what we cannot talk about we must pass over in silence. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23097
|
| Posted: Sun Feb 09, 2025 2:55 pm Post subject: |
|
|
| I would expect that the /run/user/uid directories should be mode 700. The question then is why these programs are trying to poke around in run directories other than their own. This is probably due to an incorrect environment variable instructing them to look there. |
|
| Back to top |
|
|
Da51d
n00b
Joined: 27 Mar 2024
Posts: 62
|
| Posted: Mon Feb 10, 2025 11:29 am Post subject: |
|
|
Evolution (now reinstalled) also works fine with the environment variable NO_AT_BRIDGE=1. So it solves my problem...however probably not useful for someone who requires assistive technology.
| Quote: | | This is probably due to an incorrect environment variable instructing them to look there |
The SESSION_MANAGER environment variable is empty, with an i3 session. There is also a difference between the lightdm processes running prior to logging in with and without NO_AT_BRIDGE=1.
WIth:
| Code: | root 2132 0.0 0.0 305628 7112 ? Ssl 01:03 0:00 /usr/sbin/lightdm
root 2198 0.1 0.9 759700 74300 tty7 Ssl+ 01:03 0:00 /bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
root 2238 0.0 0.0 233596 7808 ? Sl 01:04 0:00 lightdm --session-child 17 20
lightdm 2242 0.2 0.9 839260 77780 ? Ssl 01:04 0:00 /bin/lightdm-gtk-greeter
lightdm 2247 0.0 0.0 378484 6656 ? Sl 01:04 0:00 /usr/libexec/at-spi-bus-launcher --launch-immediately
lightdm 2256 0.0 0.0 4368 1664 ? S 01:04 0:00 dbus-launch --autolaunch=8a55c654a3d71d4d27888bc0673e9427 --binary-syntax --close-stderr
lightdm 2258 0.0 0.0 5668 1792 ? Ss 01:04 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
lightdm 2261 0.0 0.0 4568 2816 ? S 01:04 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/134/at-spi/bus_0
root 2267 0.0 0.0 12240 5888 ? S 01:04 0:00 lightdm --session-child 13 20 |
Without:
| Code: | root 2125 0.0 0.0 305628 6816 ? Ssl 01:15 0:00 /usr/sbin/lightdm
root 2194 0.2 0.9 760192 74320 tty7 Ssl+ 01:15 0:00 /bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
root 2250 0.0 0.1 233596 8064 ? Sl 01:15 0:00 lightdm --session-child 17 20
lightdm 2254 0.2 0.9 839348 77528 ? Ssl 01:15 0:00 /bin/lightdm-gtk-greeter
lightdm 2261 0.0 0.0 4368 1792 ? S 01:15 0:00 dbus-launch --autolaunch 8a55c654a3d71d4d27888bc0673e9427 --binary-syntax --close-stderr
lightdm 2262 0.0 0.0 5668 2048 ? Ss 01:15 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
lightdm 2264 0.0 0.0 378484 6528 ? Sl 01:15 0:00 /usr/libexec/at-spi-bus-launcher
lightdm 2270 0.0 0.0 5648 2944 ? S 01:15 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/134/at-spi/bus_0
root 2287 0.0 0.0 12240 5888 ? S 01:15 0:00 lightdm --session-child 13 20
lightdm 2289 0.0 0.0 231412 6784 ? Sl 01:15 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session |
My attention is drawn to "--use-gnome-session" in the latter case. Gnome-session is not installed.
Also, after logging in -
With:
| Code: | root 2132 0.0 0.0 305788 7240 ? SLsl 01:03 0:00 /usr/sbin/lightdm
root 2198 0.1 0.8 697712 70844 tty7 Ssl+ 01:03 0:00 /bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
lightdm 2256 0.0 0.0 4368 1664 ? S 01:04 0:00 dbus-launch --autolaunch=8a55c654a3d71d4d27888bc0673e9427 --binary-syntax --close-stderr
lightdm 2258 0.0 0.0 5668 1792 ? Ss 01:04 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
root 2267 0.0 0.1 233596 8064 ? Sl 01:04 0:00 lightdm --session-child 13 20
root 2405 0.0 0.0 6528 2176 tty5 S+ 01:08 0:00 grep --color=auto lightdm |
Without:
| Code: | root 2125 0.0 0.0 305788 6944 ? SLsl 01:15 0:00 /usr/sbin/lightdm
root 2194 0.1 0.8 706112 70992 tty7 Ssl+ 01:15 0:00 /bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
lightdm 2261 0.0 0.0 4368 1792 ? S 01:15 0:00 dbus-launch --autolaunch 8a55c654a3d71d4d27888bc0673e9427 --binary-syntax --close-stderr
lightdm 2262 0.0 0.0 5668 2048 ? Ss 01:15 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
lightdm 2264 0.0 0.0 378484 6528 ? Sl 01:15 0:00 /usr/libexec/at-spi-bus-launcher
lightdm 2270 0.0 0.0 5648 2944 ? S 01:15 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/134/at-spi/bus_0
root 2287 0.0 0.1 233596 8064 ? Sl 01:15 0:00 lightdm --session-child 13 20
lightdm 2289 0.0 0.0 231544 6912 ? Sl 01:15 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
root 2434 0.0 0.0 6528 2176 tty3 S+ 01:20 0:00 grep --color=auto lightdm |
Anyway, the problem is solved for me. I suppose anyone who requires assistive technology can simply install Gnome Desktop and they won't have a problem. At-spi is Gnome's baby after all.
Thanks everyone for the help.
_________________
What can be said at all can be said clearly and what we cannot talk about we must pass over in silence. |
|
| Back to top |
|
|
|
Desktop Environments
