Bluez 4.x changed some of the dbus apis around. In this case, audio runs
inside of blutoothd (new name of hcid) and so uses the org.bluez
destination and not a dynamic destination looked up with ActivateService.
(the bluez 4.x method for connecting an audio device is shown in the
pulseaudio-specific part of
http://wiki.bluez.org/wiki/HOWTO/AudioDevices, which I excerpt below)
$ dbus-send --print-reply --system --dest=org.bluez /
org.bluez.Manager.DefaultAdapter
method return sender=:1.18141 -> dest=:1.18218 reply_serial=2
object path "/org/bluez/4189/hci0"
$ dbus-send --print-reply --system --dest=org.bluez /org/bluez/4189/hci0
org.bluez.Adapter.FindDevice string:00:15:0E:A0:6C:C8
method return sender=:1.18141 -> dest=:1.18221 reply_serial=2
object path "/org/bluez/4189/hci0/dev_00_15_0E_A0_6C_C8"
$ dbus-send --print-reply --system --dest=org.bluez
/org/bluez/4189/hci0/dev_00_15_0E_A0_6C_C8 org.bluez.AudioSink.Connect
method return sender=:1.18141 -> dest=:1.18226 reply_serial=2
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
