From systemd journal: Aug 18 22:01:08 localhost pulseaudio[847]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. Solution: # systemctl enable bluetooth.service Created symlink /etc/systemd/system/dbus-org.bluez.service → /usr/lib/systemd/system/bluetooth.service. Created symlink /etc/systemd/system/bluetooth.target.wants/bluetooth.service → /usr/lib/systemd/system/bluetooth.service. Sources: https://bbs.archlinux.org/viewtopic.php?pid=1214447#p1214447 https://bugs.archlinux.org/task/32427 Maybe some postinstall message could be added to bluez to make users aware of this unexpected solution? Reproducible: Always
This is not bluez specific, for example, bug 567798 shows exactly the same. In summary, the problem is that systemd error message is to cryptic to let admin to really know what to do (or, if the the message is really important ever)
(In reply to Pacho Ramos from comment #1) You added the UPSTREAM keyword to this bug; can you share a link to the upstream bug report?
I didn't report it... I wanted for others knowing more about this if we should add a note to the wiki page or report it... since it's not clear to me what is the responsible of showing that messages It hasn't ever been clear to me what should an admin do when he sees the messages... then, I wanted some "expert" to clarify this before trying to document it or tell upstream systemd to do "something" https://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation https://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services
I don't really see a general solution to this, other than enabling dbus-based services by default. It does seem worth asking systemd and dbus upstream about it.
