Failed to connect to bus: No medium found

Troubleshooting
1

Creating a bug report/issue

Required Information

  • DietPi version | cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=22
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
bookworm 0
  • Kernel version | uname -a
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
  • Architecture | dpkg --print-architecture
arm64
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
RPi 4 Model B (aarch64)

Steps to reproduce

  1. systemctl --user enable pipewire.service
  2. Failed to connect to bus: No medium found

Expected behaviour

  • success

Actual behaviour

  • Failed to connect to bus: No medium found

Extra details

  • dbus logind active
2

interesting:

root@DietPi:~# loginctl show-user dietpi
Failed to get user: User ID 1000 is not logged in or lingering
  1. logged in via ssh
  2. linger is enabled
3

apt install dbus-user-session

2 Likes
4

yes we don’t install dbus by default.

5

Just in case others land here: For the loginctl command to work, additionally logind needs to be unmasked:

systemctl unmask systemd-logind
systemctl start systemd-logind
2 Likes
6

Sorry to revive this old thread, but I just wanted to share that I also had to unmask and start systemd-logind as mentioned in the last post, other than installing dbus-user-session.
Thank you!
My os: latest DietPi bookworm on Asus Tinkerboard.