** Description changed:
- All my A2DP devices can't create a audio device properly...
+ All my A2DP profile devices can't create a audio device properly...
My 2 13.04 machines both have this issue(1 notebook, 2 bluetooth dongles)
+ UPDATE: Upgraded to 13.10, still reproducible
ProblemType:
I can confirm @trshemanske's fix does the magic, THANKS!
** Summary changed:
- A2DP audio sink devices failed to work with bluetoothd : Unable to select
SEP in system log.
+ PulseAudio doesn't load bluetooth modules automatically(A2DP audio sink
devices failed to work with bluetoothd : Unable
After several hours of googling and trying various suggested fixes, I
have my bluetooth speakers working and have some hints. Hopefully
package maintainers et al can coax them into a more usable form
First and foremost I found the following two URLs of enormous help:
I am running the 64 bit version of Ubuntu 13.10 and face the same
problem with Unable to select SEP errors in syslog. The suggestion in
comment #7 unfortunately did not solve the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Comment #7 by Erik is a workaround but not a all-time solution(this
requires HF(S)P/A2DP dual profile device, but there's bluetooth speaker
didn't support HF(S)P profile)
Comment #9 mentioned bug #1179801, which I suspect it is not the exact
same issue.
--
You received this bug notification
I am running the same packages as in comment #9 (however, under 13.10
alpha 2) but to no avail.
ii bluez 4.101-0ubuntu8b1 amd64
ii pulseaudio 1:4.0-0ubuntu2+b amd64
Apparently, downgrading to 12.10 versions fixes the problem, as has been
reported here:
After removing and installing various versions of pulseaudio and bluez,
finally keeping the latest version of bluez [bluez (4.101-0ubuntu8b1)
raring] and updating pulseaudio from the saucy ppa to version 4.0 solved
my problems. I now can connect via A2DP to my bluetooth enabled
speakers.
--
You
I am running the 64 bit version of Ubuntu 13.04 and face the same
problem with Unable to select SEP errors in syslog. The suggestion in
comment #7 unfortunately did not solve the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This helped resolve the problem for me:
In /etc/bluetooth/audio.conf:
HFP=false
...
[A2DP]
SBCSources=1
MPEG12Sources=0
Source: https://bbs.archlinux.org/viewtopic.php?id=157326
Under [General], I also added Enable=Source,Media but this may not be
necessary.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1199059
Title:
A2DP
I am having a similar issue. My log does not contain the Host issue, but
does have the SEP problem. I can pair, but when connecting to the
device, Blueman responds with Connection failed: Stream setup failed.
Log from bluetoothd contains the following:
bluetoothd[2588]: audio/avdtp.c:avdtp_ref()
I'm not quite remember all the process, but I sure tried re-connecting
dongle, re-pairing, and re-setuping the A2DP device a few times.
I can successfully pair the A2DP device but It just not working.
Here's the hcidump and syslog diff of just try to connect the device
Vdragon@Vubuntu ~ % tail
It seems that you closed the hci device before the hci messages.
Jul 9 00:45:20 Vdragon-PC1 bluetoothd[997]: Host is down (112)
Jul 9 00:46:04 Vdragon-PC1 bluetoothd[997]: Unable to select SEP
And I see the following logs, are you making the pair or connection and reset
the dongle on purpose?
** Attachment added: hcidump
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/+attachment/3729446/+files/hci.log
** Description changed:
- All my A2DP device can't create a audio device...
+ All my A2DP devices can't create a audio device properly...
+ My 2 13.04 machines have
14 matches
Mail list logo
