[Pkg-bluetooth-maintainers] Bug#532018: Bug#532018: poorly documented

Harald Dunkel harald.dunkel at t-online.de
Sun Jun 7 05:12:52 UTC 2009


Filippo Giunchedi wrote:
> On Sat, Jun 06, 2009 at 06:51:21PM +0200, Filippo Giunchedi wrote:
>> I'd rather not play with the storage itself, the dbus API provides means for
>> bonding devices thus I'll try to document that.
>>
>> I'd like if you can try this:
>>
>> dbus-send --system --print-reply --dest=org.bluez / \
>> org.bluez.Manager.DefaultAdapter
>>
>> this will give you an object path with the default adapter.
>> Start bluetooth-agent providing a passkey, then:
> 
> err, actually bluetooth-agent won't work, I'm working on a patch
> 

Please mail, I would be glad to verify the procedure you had sent.

Whats wrong with the pincodes file? I know it is not the "blessed"
way, but this is much closer to what I would expect in the Unix
world.

BTW, bluez-alsa has a very short list of dependencies. Esp. there
is no dbus. Is this correct?


Regards

Harri


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-bluetooth-maintainers/attachments/20090607/b81a9a45/attachment.pgp>


More information about the Pkg-bluetooth-maintainers mailing list