I have barebones raspbian, i.e. basically Debian 8, with systemd and no X. I removed dbus with "apt-get remove dbus". It deinstalled cleanly, with no apparent programs depending on it. Now, whenever I login on the console after the motd I get this line:
Failed to get D-Bus connection: No such file or directory
What's the source of that message, and how can I make it stop? Must be something somewhere in /etc I can set, right?
It looks like systemd still thinks there is a dbus. There is still a dbus.service which I manually disabled with systemctl, just to be sure. It complained (inserv warning current start runlevel(s) (empty) of script dbus overrides LSB defaults ....) but, all my services do seem normal; I don't know for sure. Running "systemctl start anythinghere" as non-root produces the same error. So user-level privilege systemd, whatever it is called, appears to be the source but I don't have systemd-logind running on my system, and I don't understand how /bin/login is calling systemd.
raspios-bullseye-arm64-lite.img.xz
a Debian based distribution for RasberryPi board. It solved with installing all packages with starts with dbus:apt install dbus*