> On May 17, 2016, at 1:14 AM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > <snip> > Regarding the actual problem it is probably because experimental > interfaces are not enabled by default, you can do enable that by > passing -E to bluetoothd. If you’re using systemd, the file you’ll want to tweak is /lib/systemd/system/bluetooth.service Modify your ExecStart line to include the -E option. Mine currently looks like: ExecStart=/usr/lib/bluetooth/bluetoothd -d -E --noplugin=* The -d is indispensable and took my a while to stumble upon. Any python error you have that is fired by dbus callbacks will not show up on the stdout/stderr of you program (e.g. an error downstream of a WriteValue() callback). Rather it will show up in the debug output of the bluetooth daemon. So I pretty much always have journalctl -flu bluetooth running when I’m changing things, so I can see those errors reported there. By default, you get a whole bunch of stuff in your dbus namespace from older stuff. The —noplugin=* flag gets rid of all of those, so you’ll only see your own stuff in the dbus tree. -- 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
