On 12/25/22 11:11, 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.
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) 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. 3. sshd PAM configuration does not use pam_systemd 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.
This seems to come from spurious carriage returns generated by environment variables setting BASH_FUNC_* Firstly: Happens with ssh from Tumbleweed or Leap 15.4 to Leap 15.4 Affects only bash, tcsh does not show this error. This error depends on which packages are installed Setting verbose in /etc/profile.d/openssh-dbus.sh shows variables that are set, but that are on two lines (the last line being a single closing brace "}"), so this single character is probably being attempted to be set as an environment variable (which does not work). The variables being set on my instance are: BASH_FUNC_module%%, BASH_FUNC_mc%%, and BASH_FUNC_ml%%. These are the only variables with the BASH_FUNC_ prefix. Removing these packages (Lmod and MC: 'zypper remove lua-lmod mc') eliminates the error. I have not found the source that is setting the variables, but I imagine that since there is already an open case, it will be found and corrected. -- Patrick McNeil Université de Montréal - TI Pav. Roger-Gaudry, Y-201-11b ☎ Téléphone: (514) 343-6111, poste 5247 📧 Courriel: patrick.mcneil@umontreal.ca 📠 Télécopie/FAX: (514) 343-2155