> Even if there is some problem with dbus-daemon, this must not prevent > blueman installing - requiring a reboot to complete an installation is > not acceptable.
This is not a blueman issue as it's not blueman that asks for the reboot. blueman requires the dbus configuration to be reloaded (it will not work otherwise, so it makes sense configuring fails). The problem you have is that your dbus configuration files are not valid for the dbus version you're running, so a reload is not possible. Here's the report for this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793519 You should be able to configure the blueman package with --no-triggers to reach a more complete state, but reaching the installed state and especially getting blueman working won't work without fixing your dbus issue first. I think restarting dbus should be enough to fix your state and get blueman to install, but it will break so many things on your system that it's probably indeed a reboot you want.
