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: 61
|
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: 61
|
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: 61
|
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: 61
|
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 |
|
|
|