Hi Brendan, On Mon, Mar 25, 2013, Brendan West wrote: > That sounds like it could be the problem. However, shouldn't the old > bluetoothd stop and the new one start when I reboot the Raspberry Pi? > Or do I actually have to do it manually? If the latter, can you > explain how to do so (I am not sure how two different versions can be > installed at the same time..I was under the impression that a normal > install of the new would overwrite the old). BlueZ 5.x installs bluetoothd by default into /usr/libexec/bluetooth/ whereas 4.x installs it to /usr/sbin/, so it wouldn't get overwritten. > As for the D-Bus policy, I'm afraid that I am still not sure how to do > that one either.. I have updated D-Bus using apt-get, but you seem to > be referring to something else.. Would you mind explaining further? D-Bus policy files are provided by each service that needs them. You won't get the new BlueZ policy with some centralized D-Bus package. I tried to tell you that you'll find the policy file in the BlueZ source tree and you just need to copy it to the right place (also explained in my email). Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
