The `machinectl shell` command stopped working after systemd upgrade to 250.2-1

Support Virtualization
1

Hello!

After systemd upgrade from 249.7-2 to 250.2-1, the machinectl shell command stopped working. The console output:

$ sudo machinectl shell vas@deb3
Connected to machine deb3. Press ^] three times within 1s to exit session.
Connection to machine deb3 terminated.

The machine deb3 is alive however, it can be entered via machinectl login deb3.

The journal inside the virtual machine (a Debian container set up as described in archlinux wiki article “Systemd-nspawn#Create_a_Debian_or_Ubuntu_environment”) prints the following error:

deb3 systemd[1]: container-shell@9.service: Succeeded.
deb3 systemd[1]: container-shell@9.service: Consumed 1ms CPU time.
deb3 systemd[1]: Started Shell for User vas.
deb3 systemd[1313]: Assertion 'a' failed at ../src/basic/path-util.c:433, function path_compare(). Aborting.
deb3 systemd[1]: container-shell@9.service: Main process exited, code=dumped, status=6/ABRT

Downgrading systemd to 249.7-2 is a workaround. Trying to google up the above error message has not resulted in any enlightenment.

I could file a more formal bug report, where is the right place for issue reporting?

2
3

If you think the bug is upstream and not in Arch/Manjaro, here you are: Message "Assertion 'a' failed at ../src/basic/path-util.c:433, function path_compare(). Aborting." when running `machinectl shell` · Issue #22234 · systemd/systemd · GitHub

4

So, this issue has already been fixed in the upstream. In the systemd issue Message "Assertion 'a' failed at ../src/basic/path-util.c:433, function path_compare(). Aborting." when running `machinectl shell` · Issue #22234 · systemd/systemd · GitHub they concluded “Hence, please contact to your distro to backport the commit. There is nothing we can do in upstream.”

So, how do I contact the Manjaro distro team to report the problem?