I run up to date x86_64 artix with runit init. I have dbus 1.16.2-1.1 and it has these run scripts
/etc/runit/sv/dbus/run
#!/bin/sh
dbus-uuidgen --ensure=/etc/machine-id
[ -d /run/dbus ] || install -m755 -g 81 -o 81 -d /run/dbus
exec dbus-daemon --system --nofork --nopidfile
and /etc/runit/sv/dbus/log/run
#!/bin/sh
exec 2>&1; set -e
[ -d /var/log/dbus ] || install -dm 755 /var/log/dbus
exec svlogd -tt /var/log/dbus
All the processes appear to be running as expected eg ps shows
runsv dbus
svlogd -tt /var/log/dbus
dbus-daemon --system --nofork --nopidfile
however, in the runsvdir proctitle log I see this
runsvdir -P /run/runit/service log: ve keysym XF86DoNotDisturb Errors f.......lly (0). Closing log file. dbus-daemon[1257]: [system]....ctivated service 'org.freedesktop.login1'
the log in /var/log/dbus/current ends with
2022-11-21_14:41:43.25838 wlan0: CTRL-EVENT-TERMINATING
so this file is not being written with modern logs. The running daemon is called
dbus-daemon and it's log gets closed. This runit setu goes back a long way so is there something I need to rename to get the dbus logs? Perhaps
/etc/runit/dbus should be
/etc/runit/dbus-daemon or?
That's an oversight in the package script. There should be a 2>&1 at the end of the exec dbus-daemon ... line.
That "Closing log file" is probably from another program, readproctitle mixes up everything that has a non-redirected stderr.
Since there's no "--nosyslog" argument in the run script, maybe you can find dbus's logs in metalog/syslog-ng/etc.'s output.
Thanks; yes that works fine. I get the following new log
2025-05-10_07:19:39.80289 dbus[2108]: Unknown username "pulse" in message bus configuration file
now I wonder what/where is message bus configuration file. I see that /usr/share/dbus-1/system.d/pulseaudio-system.conf contains a reference to pulse, but passwd has no such user.
AFAIK, /usr/share/dbus-1/system.conf and the system.d folder next to it are merged as the configuration when the "main" (system-wide) D-Bus is loaded. I think your diagnosis of the cause is correct.
I wouldn't worry about it though, since PulseAudio by default runs per-user and you have to go out of your way to make it system-wide.