Re: Can't enable 66 after migration from s6
Reply #49 –
Just booted both my desktop and laptop today, and the error is back! Are you sure this is tested? Maybe the code for dbus in 66 should follow the one by Dudemanguy for s6, because there I didn't have any problems with dbus since November.
I'm going to (try to) temporarily reinstall s6 again since I need Viber today for work, then back to debugging 66.
Edit: Managed to reinstall. Here's what dbus-s6 is doing:
#!/usr/bin/execlineb -P
foreground { dbus-uuidgen --ensure=/etc/machine-id }
foreground { install -m755 -g 81 -o 81 -d /run/dbus }
foreground {
envfile /etc/s6/config/dbus.conf
importas -iu DBUS_UUIDGEN DBUS_UUIDGEN
if { test ${DBUS_UUIDGEN} = "yes" }
redirfd -w 1 /etc/machine-id dbus-uuidgen
}
fdmove -c 2 1
exec dbus-daemon --system --nofork --nopidfile --print-pid=3
So, essentially, it calls dbus-uuidgen --ensure=..., before setting up the socket, and then again the equivalent of dbus-uuidgen > /etc/machine-id, but the latter only if the variable DBUS_UUIDGEN is set to a value (in dbus-s6, the value is "yes"). Finally, dbus-daemon is called regardless of the outcome of the test.