← Back to team overview

blueman team mailing list archive

[Bug 350479] Re: A2DP doesn't automatically configure when service connects

 

I can't using my bluetooth stereo headset Plantronics 590 in Jaunty 9.04 rc with Blueman 1.10
I make all steps, described in notes - pair device with blueman, enable using plugin PulseAudio. After trying "Connect A2DP Services" I see "Success" as result, but new audio device didn't appear in padevchooser, also in logs has some errors:

bluetoothd[5231]: link_key_request (sba=00:1A:7D:0A:B7:BB, dba=00:19:7F:1B:EA:E2)
kernel: [ 4480.154486] input: 00:19:7F:1B:EA:E2 as /devices/virtual/input/input23
pulseaudio[4118]: module-bluetooth-device.c: BT_GET_CAPABILITIES failed : Input/output error(5)
pulseaudio[4118]: module-bluetooth-device.c: Failed to expect for GETCAPABILITIES_RSP
torba pulseaudio[4118]: module-bluetooth-device.c: Failed to get device capabilities
torba pulseaudio[4118]: module.c: Failed to load  module "module-bluetooth-device" (argument: "address=00:19:7F:1B:EA:E2 profile=a2dp"): initialization failed.

Does needs some changes in ~/.asoundrc? Does it need more?

-- 
A2DP doesn't automatically configure when service connects
https://bugs.launchpad.net/bugs/350479
You received this bug notification because you are a member of Blueman
Development Team, which is the registrant for Blueman.

Status in Blueman - Bluetooth Manager: Fix Committed

Bug description:
When you successfully connect to an A2DP service (headphones, gateways, etc.), your audio does not automatically route to those devices. In fact, they do not even show up as sinks for the PulseAudio Device Chooser. It would be nice to automatically add config options so they can be easily switched to.