The problem appears to be with setting up the input sink, which I
couldn't care less about. If any knows of a way for bluez / pulseaudio
to force a device to just connect as an output-only device (e.g., normal
bluetooth speaker), I think I'd be fine, as I have no problems with
numerous other bluetooth speakers.
If not, I think for me the key is to figure out why the input sink
cannot be established due to the "device or resource busy" message. If
I could figure out how to a detailed debug / strace of bluetoothd when
it tries to establish the input sink, that'd be most helpful. I've
tried before w/o finding anything helpful.
For me, I think the issue is not with pulseaudio but truly with bluez.
Given this, I'd like to request that my bug 1691556 be re-opened and
unmarked as a duplicate. From my perspective, no evidence or
explanation has been given for why my report was marked as a duplicate
as this one. The errors I've been continually reporting are different
than those reported by others, and the fixes that seem to work for
others do not work for me.
For the record, here are the pulseaudio and bluez packages I presently
have installed on my Ubuntu 16.04.02 LTS 64-bit on an Intel NUC i5
(NUC5i5RYH):
--------------------
```
morse@n1 intel-nuc-i5-n1> dpkg -l bluez* pulsea*
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version
Architektur Beschreibung
+++-===============================================-============================-============================-===================================================================================================
ii bluez 5.37-0ubuntu5
amd64 Bluetooth tools and daemons
un bluez-alsa <keine>
<keine> (keine Beschreibung vorhanden)
un bluez-audio <keine>
<keine> (keine Beschreibung vorhanden)
ii bluez-cups 5.37-0ubuntu5
amd64 Bluetooth printer driver for CUPS
un bluez-gnome <keine>
<keine> (keine Beschreibung vorhanden)
un bluez-input <keine>
<keine> (keine Beschreibung vorhanden)
un bluez-network <keine>
<keine> (keine Beschreibung vorhanden)
ii bluez-obexd 5.37-0ubuntu5
amd64 bluez obex daemon
un bluez-serial <keine>
<keine> (keine Beschreibung vorhanden)
un bluez-utils <keine>
<keine> (keine Beschreibung vorhanden)
ii pulseaudio 1:8.0-0ubuntu3.3~xenial1
amd64 PulseAudio sound server
un pulseaudio-esound-compat <keine>
<keine> (keine Beschreibung vorhanden)
ii pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3~xenial1
amd64 Bluetooth module for PulseAudio sound server
ii pulseaudio-module-gconf 1:8.0-0ubuntu3.3~xenial1
amd64 GConf module for PulseAudio sound server
ii pulseaudio-module-x11 1:8.0-0ubuntu3.3~xenial1
amd64 X11 module for PulseAudio sound server
ii pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3~xenial1
amd64 Zeroconf module for PulseAudio sound server
ii pulseaudio-utils 1:8.0-0ubuntu3.3~xenial1
amd64 Command line tools for the PulseAudio sound server
```
--------------------
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1582213
Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first
Status in bluez package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
In Progress
Bug description:
[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.
[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Verify in Sound settings you have it set to A2DP mode.
3. Turn off and then on the Bluetooth device.
4. Verify the device has reconnected and if not, force it to in the Bluetooth
indicator menu.
5. Open Sound settings again, select the device and verify it's reappeared in
A2DP mode.
6. Click 'Test Sound'.
Expected: Sound can be heard from the Bluetooth device.
[Regression Potential]
Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main
area affected. A combination of related A2DP bugs in pulseaudio in xenial means
it is difficult to get working at all without this patch. So highly unlikely
Bluetooth audio support could get worse. Since pulseaudio itself is being
modified there is always a regression potential in support for other audio
devices, but several audio devices have been tested and all continue to work
well with the patch.
[Other notes]
Related to bug 1283003 and bug 1438510. Possibly others too.
Please note that Bluetooth and Bluetooth audio support in xenial is
still not perfect. This SRU only aims to address a few of the most
troublesome issues. Please consider the fact that this is an
incremental improvement and some people are still likely to experience
some bugs related to pulseaudio and Bluetooth, even after this SRU.
The patch was authored by Luke Yelavich with help from Konrad
Zapałowicz. And it has received further testing over the past two
months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
here only changes the changelog wording from Luke's original PPA.
[Original Description]
I have a Sennheiser MM 450-X headset.
In 15.10, connection & playback was straightforward.
In 16.04, the headset connects, and shows up as default playback
device on `pavucontrol`, but there is no sound.
A functional workaround is to, after having connected it, to go the
`Configuration` tab, and in the `Profile` dropdown, to choose `...
HSP/HFP`, which will make them play as expected (but in low quality),
then switch to `... A2DP Sink` (they will play in high quality).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: myuser 2936 F.... pulseaudio
/dev/snd/controlC2: myuser 2936 F.... pulseaudio
/dev/snd/controlC0: myuser 2936 F.... pulseaudio
Date: Mon May 16 14:18:58 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-11 (66 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XN-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
