Hi On Mon, Apr 20, 2009 at 10:27 PM, yesir yao <yesiryao@xxxxxxxxx> wrote: > hi, all: > > I need to use dbus api to control my bluetooth adapter in my C program. > After I had read doc/adapter-api.txt and writed the codes, It can't work The answer is very simple, you are using fixed/hardcoded object path (/org/bluez/hci0) that is causing the problem. We made sure it won't work by adding the pid to the path so no one will have a change to hardcode an adapter path and the code still work after bluetoothd has restarted, the correct way of doing this is via '/' path (the only fixed path bluetoothd has) which implements org.bluez.Manager (see doc/manager-api.txt). About the G_DBUS_METHOD_FLAG_ASYNC are really not for clients, although they hint the behavior of the daemon the client should know better whether to block or not. ps: check this http://smcv.pseudorandom.co.uk/2008/11/nonblocking/ -- Luiz Augusto von Dentz Engenheiro de Computação -- 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
