Bug#1004339: /usr/bin/systemctl: `systemctl start --user --wait` fails with "Failed to connect to bus: No such file or directory"

On Tue, Jan 25, 2022 at 06:04:37PM +0100, Michael Biebl wrote: > > Control: tags -1 + moreinfo unreproducible > > Am 25.01.22 um 13:13 schrieb Adam Dinwoodie: > > > > > Failed to connect to bus: No such file or directory > > > > Thanks for the reproducer. > I can't reproduce the issue

Bug#1004339: /usr/bin/systemctl: `systemctl start --user --wait` fails with "Failed to connect to bus: No such file or directory"

Control: tags -1 + moreinfo unreproducible Am 25.01.22 um 13:13 schrieb Adam Dinwoodie: Failed to connect to bus: No such file or directory Thanks for the reproducer. I can't reproduce the issue with the instructions you provided (with v250 from sid). Your problem seems to be

Bug#1004339: /usr/bin/systemctl: `systemctl start --user --wait` fails with "Failed to connect to bus: No such file or directory"

Package: systemd Version: 250.3-1 Severity: normal File: /usr/bin/systemctl Dear Maintainer, According to the systemctl.1 man page, it should be possible to specify `--wait` to systemctl commands that will start units, to have the systemctl command block until the units terminate again. This