Unable to add a dbus user session as a service to raspberry Pi zero 2 W image
"John" <[email protected]>
| Newsgroups | org.yoctoproject.lists.poky |
|---|---|
| Message-ID | <[email protected]> |
I've been trying to add pulseaudio as a service to my raspberry Pi image (core-image-minimal) for a few days now. As pulseaudio apparently requires to be added as a d-bus user session only, I then tried to start a user session in systemd. No Joy! I have dbus running as a service but it is a system level service and not a user level service: root@raspberrypi0-64-wf:~# systemctl status dbus.service ● dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Tue 2025-02-25 21:28:52 UTC; 2min 40s ago Invocation: 95ded9e8656b41abb16c48c6e1ace29c TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 217 (dbus-daemon) Tasks: 1 (limit: 249) CPU: 222ms CGroup: /system.slice/dbus.service └─217 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only When I try to start a user session: > > root@raspberrypi0-64-wf:~# systemctl --user enable dbus.service > Failed to connect to user scope bus via local transport: > $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using > --machine=<user>@.host --user to connect to bus of other user) > I've not managed to find any examples of d-bus running as a user session. Is there some secret sauce that I'm missing? I did try to run pulseaudio as a system service, it was a blood bath (I refer to the amount of red error messages) Cheers!!