[Pkg-bluetooth-maintainers] Bug#532098: is silent, but mplayer complains loudly
Vincent Bernat
bernat at debian.org
Sun Apr 18 00:17:07 UTC 2010
OoO En cette nuit nuageuse du dimanche 18 avril 2010, vers 00:20, je
disais:
> I get into the same problem. I would like to stress the fact that
> there is not try to contact the remote device. Running hcidump shows
> that nothing happens when we try to use the bluetooth device. Maybe it
> uses only cached information. I have this in /var/lib/bluetooth about
> my remote device:
> classes:00:0F:59:11:XX:XX 0x240404
> features:00:0F:59:11:XX:XX FFFF8F7818180080
> lastseen:00:0F:59:11:XX:XX 2010-04-17 20:20:46 GMT
> lastused:00:0F:59:11:XX:XX 2010-04-17 22:04:21 GMT
> manufacturers:00:0F:59:11:XX:XX 10 4 4866
> names:00:0F:59:11:XX:XX iCom
> pincodes:00:0F:59:11:XX:XX 0000
> I have also tried 4.63 without any luck.
For the record, using Gnome Bluetooth applet solves my problem (like I
said in another mail). It seems that bonding correctly to a bluetooth
device is far more complex than I though using command line. Despite
having used hcitool {cc,con,auth,link,key}, I did not get the files that
I get when using Gnome Bluetooth applet: linkkeys, profiles, sdp and
trusts.
Also note that the error 'BT_GET_CAPABILITIES failed : Input/output
error(5)' is really misleading. When getting capabilities, it first
tries to find a device and if it does not find one, it outputs the above
error. There is nothing sent. I have not looked the whole logic, but I
suspect that if your remote device is not in linkkeys and in profiles,
it will just be ignored.
I encourage all reporters (except Mark because I think that it tries
with a remote device that does not support A2DP) to check the content of
/var/lib/bluetooth and to try to do the pairing with Gnome Bluetooth
applet.
But maybe there was a but which is fixed in 4.60.
Moreover, I tried to test my headset with alsaplayer. alsaplayer seems
to try to open the device twice which is rejected with an error like
this:
bluetoothd[7968]: open a2dp - object=ANY source=ANY destination=00:0F:59:11:XX:XX lock=write
bluetoothd[7968]: Client already has an opened session
I have used mpg321 which does not have this problem.
I use this asoundrc:
pcm.bluetooth {
type bluetooth
device 00:0F:59:11:XX:XX
}
pcm.!default {
type plug
slave {
pcm bluetooth
}
}
--
> c'est ce con appelle une remarque idiote
-+- AM in Guide du Neuneu Usenet : Le mta-neuneu est arriv -+-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-bluetooth-maintainers/attachments/20100418/dba02e24/attachment.pgp>
More information about the Pkg-bluetooth-maintainers
mailing list