On Sonntag, 25. Dezember 2022 17:11:07 CET Andrei Borzenkov wrote:
On 25.12.2022 17:16, mh@mike.franken.de wrote:
On Sonntag, 25. Dezember 2022 15:11:05 CET Andrei Borzenkov wrote:
On 25.12.2022 16:54, mh@mike.franken.de wrote:
On Sonntag, 25. Dezember 2022 14:46:50 CET Andrei Borzenkov wrote: [...]
What is output of
env systemctl --user show-environment
in ssh session?
My environment is huge and it contains lots of functions, but I'm not sure, why this is relevant, because the environment is much larger when reaching the command prompt. At the point, /etc/profile.d/openssh-dbus.sh is running, there are only about 20 variables. Wouldn't it be more interesting to see the env variables at this point?
Which is already what I asked you.
Uhm, then I misunderstood you or I didn't find the correct wording. I meant the env vars that /etc/profile.d/openssh-dbus.sh is seeing.
show
env | grep DBUS
myuser 26702 1 0 11:09 ? 00:00:00 /usr/bin/dbus-daemon --syslog- only --fork --print-pid 5 --print-address myuser 26788 1 0 11:09 ? 00:00:00 /usr/bin/xconsole -file /dev/ xconsole -bg gainsboro -daemon -display loc myuser 26795 26792 0 11:09 ? 00:00:00 sshd: myuser@pts/1 myuser 26796 26795 0 11:09 pts/1 00:00:00 -bash
empty
That should not be so.
The only way I can reproduce your error is
1. There is already systemd user instance running (at least, /run/users/$UID/systemd exists)
exists
2. There is no default session dbus socket (/run/users/$UID/bus) which is already something that should not happen - it is created automatically by systemd user instance.
doesn't exist
3. sshd PAM configuration does not use pam_systemd
how can I check this?
4. Something sets manually XDG_RUNTIME_DIR
I have no idea how you can get into this situation. Check mentioned files/directories. As you refused to show environment, we also do not know whether XDG_RUNTIME_DIR is set and to which value.
echo $XDG_RUNTIME_DIR /run/user/10000