Can't connect to A2DP Device in Ubuntu 13.04

Bug #1179801 reported by billy3321
318
This bug affects 73 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I just upgrade my system from Ubuntu 12.04.1 to Ubuntu 13.04. And I found my bluetooth headset which work on Ubuntu 12.04.1 can not work on 13.04. My laptop is lenovo X200.

While I setup the device as Audio Sink with Blueman, It always report "Device added, but connection failed.". And if just set it as Audio Sink, It report "Stream setup failed".

I check /var/log/syslog, and found the bluetoothd has some error report:

bluetoothd[6054]: Permission denied (13)

if I run bluetoothd with command "bluetooth -dn", the error output:

bluetoothd[6231]: audio/avdtp.c:avdtp_ref() 0x7fbd674d4de0: ref=2
bluetoothd[6231]: audio/sink.c:sink_set_state() State changed /org/bluez/6231/hci0/dev_00_11_B1_08_27_13: SINK_STATE_DISCONNECTED -> SINK_STATE_CONNECTING
bluetoothd[6231]: audio/sink.c:sink_connect() stream creation in progress
bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() cond 1
bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() Received 36 bytes from management socket
bluetoothd[6231]: plugins/mgmtops.c:mgmt_device_connected() hci0 device 00:11:B1:08:27:13 connected eir_len 17
bluetoothd[6231]: src/adapter.c:adapter_get_device() 00:11:B1:08:27:13
bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() cond 1
bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() Received 14 bytes from management socket
bluetoothd[6231]: plugins/mgmtops.c:mgmt_auth_failed() hci0 auth failed status 5
bluetoothd[6231]: src/device.c:device_bonding_complete() bonding (nil) status 0x05
bluetoothd[6231]: Permission denied (13)
bluetoothd[6231]: audio/avdtp.c:connection_lost() Disconnected from 00:11:B1:08:27:13
bluetoothd[6231]: audio/avdtp.c:avdtp_unref() 0x7fbd674d4de0: ref=1
bluetoothd[6231]: audio/sink.c:sink_set_state() State changed /org/bluez/6231/hci0/dev_00_11_B1_08_27_13: SINK_STATE_CONNECTING -> SINK_STATE_DISCONNECTED
bluetoothd[6231]: audio/sink.c:discovery_complete() connect:connect XCASE detected
bluetoothd[6231]: audio/sink.c:sink_set_state() State changed /org/bluez/6231/hci0/dev_00_11_B1_08_27_13: SINK_STATE_DISCONNECTED -> SINK_STATE_DISCONNECTED
bluetoothd[6231]: audio/device.c:device_set_state() state change attempted from disconnected to disconnected
bluetoothd[6231]: audio/avdtp.c:avdtp_unref() 0x7fbd674d4de0: ref=0
bluetoothd[6231]: audio/avdtp.c:avdtp_unref() 0x7fbd674d4de0: freeing session and removing from list
bluetoothd[6231]: audio/sink.c:stream_setup_retry() Stream setup failed, after XCASE connect:connect

My /etc/bluetooth/audio.conf file contain the line in General section:
Enable=Source,Sink,Headset,Gateway,Control,Media,Socket

My bluez version is 4.101-0ubuntu8b1, pulseaudio version is 1:3.0-0ubuntu6, and kernel is 3.8.0-19-generic x86_64.

Does anyone can help me figure out what happen and how to solve it?
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 使用者 PID 存取命令
 /dev/snd/controlC0: billy3321 3049 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=f76cdfcc-0572-42c1-8e1c-fa0ad5f31db8
InstallationDate: Installed on 2013-05-10 (4 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO 7458AJ4
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=4b12488b-151b-4153-87c2-43737dd6660e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio bluetooth cdrom dialout dip lpadmin plugdev sambashare sudo video
dmi.bios.date: 03/10/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET63WW (3.13 )
dmi.board.name: 7458AJ4
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET63WW(3.13):bd03/10/2010:svnLENOVO:pn7458AJ4:pvrThinkPadX200:rvnLENOVO:rn7458AJ4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7458AJ4
dmi.product.version: ThinkPad X200
dmi.sys.vendor: LENOVO

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1179801

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: raring
Revision history for this message
billy3321 (billy3321) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
billy3321 (billy3321) wrote : BootDmesg.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : CRDA.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : CurrentDmesg.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : IwConfig.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : Lspci.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : Lsusb.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : ProcEnviron.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : ProcInterrupts.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : ProcModules.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : PulseList.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : RfKill.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : UdevDb.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : UdevLog.txt

apport information

Revision history for this message
billy3321 (billy3321) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
billy3321 (billy3321) wrote :

I try to install the package and some error happen.

┌─ [ 08:47 billy3321@billy3321-ThinkPad-X200 ]─(~/Downloads)
└─ $ sudo LANGUAGE=C dpkg -i linux-*amd64.deb
[sudo] password for billy3321:
(Reading database ... 238701 files and directories currently installed.)
Preparing to replace linux-headers-3.10.0-031000rc1-generic 3.10.0-031000rc1.201305130510 (using linux-headers-3.10.0-031000rc1-generic_3.10.0-031000rc1.201305130510_amd64.deb) ...
Unpacking replacement linux-headers-3.10.0-031000rc1-generic ...
Preparing to replace linux-image-3.10.0-031000rc1-generic 3.10.0-031000rc1.201305130510 (using linux-image-3.10.0-031000rc1-generic_3.10.0-031000rc1.201305130510_amd64.deb) ...
Done.
Unpacking replacement linux-image-3.10.0-031000rc1-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.10.0-031000rc1-generic /boot/vmlinuz-3.10.0-031000rc1-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.10.0-031000rc1-generic /boot/vmlinuz-3.10.0-031000rc1-generic
dpkg: dependency problems prevent configuration of linux-headers-3.10.0-031000rc1-generic:
 linux-headers-3.10.0-031000rc1-generic depends on linux-headers-3.10.0-031000rc1; however:
  Package linux-headers-3.10.0-031000rc1 is not installed.

dpkg: error processing linux-headers-3.10.0-031000rc1-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-3.10.0-031000rc1-generic (3.10.0-031000rc1.201305130510) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Not updating initrd symbolic links since we are being updated/reinstalled
(3.10.0-031000rc1.201305130510 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(3.10.0-031000rc1.201305130510 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.10.0-031000rc1-generic /boot/vmlinuz-3.10.0-031000rc1-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.10.0-031000rc1-generic /boot/vmlinuz-3.10.0-031000rc1-generic
update-initramfs: Generating /boot/initrd.img-3.10.0-031000rc1-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.10.0-031000rc1-generic /boot/vmlinuz-3.10.0-031000rc1-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.10.0-031000rc1-generic /boot/vmlinuz-3.10.0-031000rc1-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.10.0-031000rc1-generic /boot/vmlinuz-3.10.0-031000rc1-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.10.0-031000rc1-generic
Found initrd image: /boot/initrd.img-3.10.0-031000rc1-generic
Found linux image: /boot/vmlinuz-3.8.0-19-generic
Found initrd image: /boot/initrd.img-3.8.0-19-generic
Found memtest86+ image: /boot/memtest86+.bin
ls: reading directory /var/lib/os-prober/mount: Software caused connection abort
done
Errors were encountered while processing:
 linux-headers-3.10.0-031000rc1-generic

Revision history for this message
EricDHH (ericdhh) wrote :

Upgraded 3 computers from 12.04 (worked well) to 13.04. No connection to creative D80 and Jabra headset.

The output device was found and rejected as "connect but sound lowering".

Revision history for this message
EricDHH (ericdhh) wrote :

Installed the fourth laptop, another bluetooth chip. Same bug, this is so annoying.....

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
EricDHH (ericdhh) wrote :

Is it possible to rollback packages to 12.10 level to get it running?

Revision history for this message
bowser (bwbernard-wong1) wrote :

Blueman always fails to connect to my srs-btx300 bluetooth speaker with the error "stream setup failed" in 13.04 (it works in 12.04 in another partition on same machine)

 However I am able to connect reliably with the gnome-bluetooth applet that comes with Ubuntu's default install. The problem with g-b applet is that it cannot find my device, however if I first run in the terminal "hcitool scan", then click "Set up New Device" on the g-b applet menu it would be able to discover the device, and once the device shows up just follow the steps and connection is established quite easilly.

Revision history for this message
bowser (bwbernard-wong1) wrote :

P.S. I am running kernel 3.10 on both 12.04 and 13.04

Revision history for this message
Steffen Sindzinski (stesind) wrote :

It throws an dbus error:

GDBus.Error:org.bluez.Error.Failed: Stream setup failed

Revision history for this message
penalvch (penalvch) wrote :

billy3321, as per http://support.lenovo.com/en_US/downloads/default.page? an update is available for your BIOS (3.22). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

tags: added: bios-outdated-3.22 needs-upstream-testing regression-release
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
billy3321 (billy3321) wrote : Re: [Bug 1179801] Re: Can't connect to A2DP Device in Ubuntu 13.04
Download full text (5.7 KiB)

Now my bios is:

6DET63WW (3.13 )
03/10/2010

I will try update my bios later.

2013/7/21 Christopher M. Penalver <email address hidden>

> billy3321, as per
> http://support.lenovo.com/en_US/downloads/default.page? an update is
> available for your BIOS (3.22). If you update to this, does it change
> anything?
>
> If not, could you please both specify what happened, and provide the
> output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-3.22 needs-upstream-testing regression-
> release
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1179801
>
> Title:
> Can't connect to A2DP Device in Ubuntu 13.04
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> I just upgrade my system from Ubuntu 12.04.1 to Ubuntu 13.04. And I
> found my bluetooth headset which work on Ubuntu 12.04.1 can not work
> on 13.04. My laptop is lenovo X200.
>
> While I setup the device as Audio Sink with Blueman, It always report
> "Device added, but connection failed.". And if just set it as Audio
> Sink, It report "Stream setup failed".
>
> I check /var/log/syslog, and found the bluetoothd has some error
> report:
>
> bluetoothd[6054]: Permission denied (13)
>
> if I run bluetoothd with command "bluetooth -dn", the error output:
>
> bluetoothd[6231]: audio/avdtp.c:avdtp_ref() 0x7fbd674d4de0: ref=2
> bluetoothd[6231]: audio/sink.c:sink_set_state() State changed
> /org/bluez/6231/hci0/dev_00_11_B1_08_27_13: SINK_STATE_DISCONNECTED ->
> SINK_STATE_CONNECTING
> bluetoothd[6231]: audio/sink.c:sink_connect() stream creation in progress
> bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() cond 1
> bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() Received 36 bytes from
> management socket
> bluetoothd[6231]: plugins/mgmtops.c:mgmt_device_connected() hci0 device
> 00:11:B1:08:27:13 connected eir_len 17
> bluetoothd[6231]: src/adapter.c:adapter_get_device() 00:11:B1:08:27:13
> bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() cond 1
> bluetoothd[6231]: plugins/mgmtops.c:mgmt_event() Received 14 bytes from
> management socket
> bluetoothd[6231]: plugins/mgmtops.c:mgmt_auth_failed() hci0 auth failed
> status 5
> bluetoothd[6231]: src/device.c:device_bonding_complete() bonding (nil)
> status 0x05
> bluetoothd[6231]: Permission denied (13)
> bluetoothd[6231]: audio/avdtp.c:connection_lost() Disconnected from
> 00:11:B1:08:27:13
> bluetoothd[6231]: audio/avdtp.c:avdtp_unref() 0x7fbd674d4de0: ref=1
> bluetoothd[6231]: audio/sink.c:sink_set_state() State changed
> /org/bluez/6231/hci0/dev_00_11_B1_08_27_13: SINK_STATE_CONNECTING ->
> SINK_STATE_DISCONNECTED
> bluetoothd[6231]: audio/sink.c:discovery_complete() connect:connect
> XCASE detected
> bluetoothd[6231]: audio/sink.c:sink_set_state() State changed
> /org/bluez/6231/hci0/dev_00_11_B1_08_27_13: SINK_STATE_DISCONNECTED ->
> SINK_STATE_DISCONNECTED
> bluetoothd[623...

Read more...

Revision history for this message
billy3321 (billy3321) wrote :

I had updated to

6DET72WW (3.22 )
10/25/2012

And bluetooth works fine. Thank you.

Revision history for this message
penalvch (penalvch) wrote :

billy3321, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1179801/comments/29 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Mehrdad Vatanparvar (m-vatanparvar) wrote :

Unfortunately, I think this bug should remain open as the problem still exist around.
The scenario is the same, everything was OK on 12.10 but after upgrading to 13.04, I get the same error when I try to setting up Audio Sink.
I use Dell XPS 17 L702x and the headset is Sennheiser MM 500-X.
By the way, I use Kubuntu 13.04 not Ubuntu and it's updated as well as Bios.
Regards,

Revision history for this message
penalvch (penalvch) wrote :

Mehrdad Vatanparvar, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Revision history for this message
Anton Anikin (anton-anikin) wrote :

I have the same problem, Ubuntu 13.10 beta

Revision history for this message
penalvch (penalvch) wrote :

Anton Anikin, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

penalvch (penalvch)
Changed in linux:
status: New → Invalid
Revision history for this message
Julie Rae Combies (curiouslymute) wrote :

Same bug in 13.10.

Revision history for this message
Bruce Braley (ciclista41) wrote :

Yes, same bug in Kubuntu 13.10 for me, also. I have BIOS 5ECN95WW(V9.00) 12/19/2012 on Lenovo G780 laptop. Everything works fine with Bluetooth when I boot to Windows 8 on same computer.

Revision history for this message
penalvch (penalvch) wrote :

Julie Rae Combies / Bruce Braley, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Revision history for this message
billy3321 (billy3321) wrote :

Does this problem solved?

now I'm using Ubuntu 13.04, I found:

If I use kernel 3.8.0-32, I can use HSP/HFP connect to my headset, but still can't use A2DP. But if I switch kernel to 3.8.0-33 or 3.8.0-34, HSP/HFP and A2DP both can't use.

Revision history for this message
penalvch (penalvch) wrote :

billy3321, given the kernel 3.8.0-32 was released Tue, 01 Oct 2013 12:43:12 -0500, after this bug was closed, and a regression in 3.8.0-33 occurred for you, this is considered a new bug, necessitating a new report. Hence, please feel free to file a new report via a terminal:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Revision history for this message
billy3321 (billy3321) wrote :

I've add the report at bug 1265745 and bug 1265742. Thanks.

Revision history for this message
billy3321 (billy3321) wrote :

@penalvch , the live system of trusty-desktop-amd64.iso daily build did not have this bug. The bluetooth headset can be connected by both A2DP and HSP/HFP.

But I will hope it can fix on next 13.10 or 13.04 kernel. 3.8.0-35 still have this bug.

Thank you.

Revision history for this message
Gabriel F. (gabriel-14-fortin) wrote :

I have the same problem in Ubuntu 13.10 when trying to connect to a Creative D100 device.

The device connects successfully but the audio sink cannot be set: "Connection Failed: Stream setup failed" message appears and the following line appears in /var/log/syslog:

May 25 20:43:18 machinename bluetoothd[763]: Unable to select SEP

I hope it helps.

Revision history for this message
penalvch (penalvch) wrote :

Gabriel F., thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
bzsolt (bodaonline) wrote :
Revision history for this message
Janus (reslayer-mail) wrote :

With formerly available gnome bluetooth applet (and lately from gnome control center) it works.
With blueman it does not (unless I kill pulseaudio process, reload alsa etc.).

Tried with headsets: CBR CHP636Bt, Creative WP-350, noname S-69.
Tried with at least 3 different onboard bluetooth chips and one USB dongle.
Tried at least 3 Ubuntu releases.

Problem remains.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueman (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Janus, please do not add bug tasks to a closed report. If you are having a problem with blueman, file a new report with Ubuntu by executing the following in a terminal:
ubuntu-bug blueman

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

no longer affects: blueman (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.