Hi, sys-apps/dbus-1.10.18 built with USE=systemd does not create a valid /usr/lib/systemd/user/dbus.service: $ cat /usr/lib/systemd/user/dbus.service [Unit] Description=D-Bus System Message Bus Requires=dbus.socket [Service] ExecStart=$bindir/dbus-daemon --session --address=systemd: --nofork --systemd-activation ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig ExecStart=$bindir/dbus-daemon should be ExecStart=/usr/bin/dbus-daemon
It's strange as the original fail contains: [Service] ExecStart=@EXPANDED_BINDIR@/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation ExecReload=@EXPANDED_BINDIR@/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig OOMScoreAdjust=-900 which is expanded by configure script. I don't see how it would change one instance and not the other. Did you try re-installing the package ?
(In reply to Gilles Dartiguelongue from comment #1) > It's strange as the original fail contains: > > [Service] > ExecStart=@EXPANDED_BINDIR@/dbus-daemon --system --address=systemd: --nofork > --nopidfile --systemd-activation > ExecReload=@EXPANDED_BINDIR@/dbus-send --print-reply --system > --type=method_call --dest=org.freedesktop.DBus / > org.freedesktop.DBus.ReloadConfig > OOMScoreAdjust=-900 > > which is expanded by configure script. I don't see how it would change one > instance and not the other. Did you try re-installing the package ? Indeed, it works fine after re-installing it