Sorry my mistake, I replied onf to Johan... On Thu, Nov 20, 2008 at 3:32 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > > Yes, as I said you'll need to fill in the proper agent callbacks (right > now there's something called "Request" which does not exist in the API) > as well as make it get the adapter path using e.g. DefaultAdapter(). All right. Thank you again! When I run this agent it is reporting here is not org.bluez DBUS service, then I verified bluetoothd is is starting correctly: # bluetoothd -nd bluetoothd[1888]: Bluetooth daemon bluetoothd[1888]: Enabling debug information bluetoothd[1888]: parsing main.conf bluetoothd[1888]: offmode=NoScan bluetoothd[1888]: discovto=0 bluetoothd[1888]: pageto=8192 bluetoothd[1888]: name=%h-%d bluetoothd[1888]: class=0x000100 bluetoothd[1888]: inqmode=0 bluetoothd[1888]: Unable to get on D-Bus This is the very same error reported here: https://lists.ubuntu.com/archives/ubuntu-bluetooth/2008-November/002629.html I am starting dbus this way: # dbus-daemon --system I tried to strace bluetoothd but it doesn't helped much, none suspect problem. Is this some specific problem of this version (4.18)? Some idea about how to solve this problem? I think "Unable to get on D-Bus" means bluetoothd are not listening to same d-bus socket started by dbus-daemon. Isn't it? > Johan Best Regards, Alan -- 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
