If the image is built with both systemd and sysvinit there'll be a dbus-1 init script and a dbus service. This means systemd can try and launch both, which won't work.
There's a systemctl mask to stop this in systemd-compat-units, but the logical place for it to be is in the dbus recipe so it can't be left out of an image. Signed-off-by: Ross Burton <[email protected]> --- meta/recipes-core/dbus/dbus.inc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc index cf17b62..db47ede 100644 --- a/meta/recipes-core/dbus/dbus.inc +++ b/meta/recipes-core/dbus/dbus.inc @@ -62,6 +62,14 @@ RRECOMMENDS_${PN}-lib = "${PN}" FILES_${PN}-dev += "${libdir}/dbus-1.0/include ${bindir}/dbus-glib-tool" pkg_postinst_dbus() { + # If both systemd and sysvinit are enabled, mask the dbus-1 init script + if ${@base_contains('DISTRO_FEATURES','systemd sysvinit','true','false',d)}; then + if [ -n "$D" ]; then + OPTS="--root=$D" + fi + systemctl $OPTS mask dbus-1.service + fi + if [ -z "$D" ] && [ -e /etc/init.d/populate-volatile.sh ] ; then /etc/init.d/populate-volatile.sh update fi -- 1.7.10.4 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
