Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3474

D-Bus socket-activation dependency problems?

$
0
0
Trying to start a plain vanilla session D-Bus with ordinary D-Bus Socket Activation at the usual unix:path=/run/user/1001/bus without a parent systemd --user process such as user@1001.service but it is fighting me every step of the way:

Code:

# Set up the socket location:$ XDG_RUNTIME_DIR="/run/user/$(id -u $USER)"$ echo $XDG_RUNTIME_DIR/run/user/1001$ export XDG_RUNTIME_DIR#Start the Systemd dbus.socket unit which will now create the listening socket:$ systemctl --user start dbus.socketFailed to connect to bus: No medium found# It wants D-Bus to initialize D-Bus!Okay loopy, we'll give you D-Bus so you can start D-Bus!$ dbus-run-session systemctl --user start dbus.socketdbus-daemon[215703]: [session uid=1001 pid=215703] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1001 pid=215704 comm="systemctl --user start dbus.socket")dbus-daemon[215703]: [session uid=1001 pid=215703] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1Failed to start dbus.socket: Process org.freedesktop.systemd1 exited with status 1See user logs and 'systemctl --user status dbus.socket' for details.# Huh? Let's see what we've got:$ echo "$DBUS_SESSION_BUS_ADDRESS"«a big fat newline prints here»#​ Total failure to create the D-Bus activation socket!# Should have been set to unix:path=/run/user/1001/bus# Should have been a short order cook.
There are no useful entries anywhere in journalctl.
Surely it must be possible to bring up a dbus.socket instance for dbus.service ...without the need for user@1001.service parent???
He HHHeeeelp!

Statistics: Posted by snovotill — 2024-05-07 08:50 — Replies 0 — Views 48



Viewing all articles
Browse latest Browse all 3474

Trending Articles