From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez-4.1: Pairing Broken?
Date: Tue, 19 Aug 2008 09:02:45 +0200 [thread overview]
Message-ID: <1219129365.7591.76.camel@violet.holtmann.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0808181917120.32359@nge2.ngu.pk>
Hi,
> I changed bluez-* to the 4.x branch. Everything went pretty smooth, despite
> massive changes. After about 4 hours, I had everything in place. I go to test
> the first connection/device, and ...
>
>
> share/dbus-1 # passkey-agent --default 0000 00:1A:45:01:F9:42 &
>
> Can't register passkey agent
> Method "RegisterDefaultPasskeyAgent" with signature "s" on interface
> "org.bluez.Security" doesn't exist
>
> [1] 4173
> [1] + exit 1 passkey-agent --default 0000 00:1A:45:01:F9:42
>
>
>
> bluez-4.1/src # Can't register authorization agent
>
> Method "RegisterDefaultAuthorizationAgent" with signature "s" on interface
> "org.bluez.Security" doesn't exist
that is expected. We remove the 3.x API. I also mentioned on
www.bluez.org that bluez-gnome will break with 4.x right now.
> bluetoothd[4803]: hcid_dbus_bonding_process_complete: status=00
> bluetoothd[4803]: hcid_dbus_bonding_process_complete: no pending auth request
> bluetoothd[4803]: Accepted new client connection on unix socket (fd=22)
> bluetoothd[4803]: Audio API: received BT_GETCAPABILITIES_REQ
> bluetoothd[4803]: Audio API: sending BT_GETCAPABILITIES_RSP
> bluetoothd[4803]: Unix client disconnected (fd=22)
>
>
>
> No! :-(
>
> media/ogg # sox -t ogg ./file.ogg -t alsa pcm.bluetooth
>
> ALSA lib pcm_bluetooth.c:1619:(bluetooth_init) BT_GETCAPABILITIES failed :
> Input/output error(5)
> sox soxio: Can't open output file `pcm.bluetooth': cannot open audio device
>
> -2- root@vdrl media/ogg # hcitool con
> Connections:
>
>
> Now all I can get are the expected authentication error type messages:
That is not a pairing issue. That is an audio service issue.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-08-19 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 0:18 [Bluez-users] bluez-4.1: Pairing Broken? jayjwa
2008-08-19 7:02 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1219129365.7591.76.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox