This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.3
---
pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium
[Luke Yelavich, Konrad Zapałowicz]
* Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
where users would experience some combination
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582213
Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode
Also verified again by me using the proposed packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582213
Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to
Yes, it's exactly the same in code. Only the changelog text was
modified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582213
Is the package in xenial-proposed exactly the same as the one in `ppa
:ubuntu-audio-dev/pulse-testing` (based on the version, I'd say so)?
If so, then I've been using it for a few weeks now, and it fixed the
problem for me.
--
You received this bug notification because you are a member of
Hello Mary, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've accepted this SRU to xenial-proposed.
Can I confirm that this bug is already fixed in yakkety and zesty? If
not, could you please upload fixes for those releases, too. We need to
ensure that upgrades don't regress.
--
You received this bug notification because you are a member of Ubuntu
("in progress" is correct, "fix commited" should be set by the SRU team
when they accept the upload according to
https://wiki.ubuntu.com/StableReleaseUpdates)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It has been sponsored but SRU go first to the "unapproved" queue where a SRU
team member need to review and accept them
https://launchpad.net/ubuntu/xenial/+queue?queue_state=1_text=pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still waiting on sponsorship. Someone unsubscribed the sponsors so I
have resubscribed them. The debdiff is in comment #8 above.
Please be careful not to confuse this with bluez. This one is about
pulseaudio, which is where bluetooth audio is implemented.
** Changed in: pulseaudio (Ubuntu
I'm not familiar with what Fix Committed means on SRUs, but will keep an eye on:
https://launchpad.net/ubuntu/+source/pulseaudio
(it's not there yet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the work Daniel, I've sponsored to Xenial let's see what the
proposed testing is going
** Changed in: pulseaudio (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done.
Also note we are working to release at least one significant update soon
for Ubuntu 16.04 Bluetooth audio support. So the PPA fixes will go
mainstream...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Daniel van Vugt (vanvugt): Thanks for your assistance!
I am not Mary Sherman, and I'm continuing to experience this problem,
even with the PPA and after rebooting.
I didn't subscribe to this bug, I didn't even know about it. I report
bug 1691556 and you marked it a duplicate of this one.
As
All,
I have spent some time looking at the major Bluetooth/audio pain points
recently. And a common problem is simply that some bugs are
oversubscribed. Everyone experiences bugs slightly differently and it
clouds the issue to the point of us not being able to ever close it.
But the answer is
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
@hife and @Mary Sherman (spot9019): Thanks for the speedy replies!
@hife: Thanks for describing your workaround in greater detail.
I've already tried the a2dp.py script, it doesn't fix the problem for
me. I just downloaded again the latest version and
@Doug Morse (dm-dougmorse): I am running Unity on Ubuntu 16.04 LTS,
Pulseaudio 1:8.0-0ubuntu3.3~xenial1, looks the same as yours. More
details of my system may be found in my duplicate report:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1651428
>From the reports you linked, I would
I'm on XFCE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
To manage notifications about
@hife and @Mary Sherman (spot9019):
You both indicate that the latest pulse-testing ppa fixes the problem
for you.
Can you both indicate whether you are running Unity as the desktop or
KDE or perhaps some other?
I still have suspicions that there may be a permissions issue that is
specific to
ppa:ubuntu-audio-dev/pulse-testing solves the problem for me.
However, now when module-switch-on-connect is not loaded, sound will
switch to bluetooth device, but neither System-Settings -> Sound nor
indicator-sound make the switch to bluetooth device, making volume
control unavailable without
I must unfortunately report that that the recently reported fix does not
work for me. Ubuntu 16.04 LTS connecting to Amazon Echo. Pulseaudio
1:8.0-0ubuntu3.3~xenial1, which is the latest presently available from
ppa:ubuntu-audio-dev/pulse-testing as of today.
The problem appears to result in
** Changed in: pulseaudio (Ubuntu Xenial)
Status: Triaged => Fix Released
** Changed in: pulseaudio (Ubuntu Xenial)
Status: Fix Released => In Progress
** Changed in: pulseaudio (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: pulseaudio (Ubuntu
** Also affects: pulseaudio (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Xenial)
Importance: Undecided
Status: New
** No longer affects: bluez (Ubuntu Xenial)
** Changed in: pulseaudio (Ubuntu)
Status: In Progress => Fix Released
Solves the problem for me (ppa:ubuntu-audio-dev/pulse-testing).
I can't comment on the reliability, since I've tested the procedure only
a few times, but I don't need anymore to perform the
disconnection/reconnection dance.
--
You received this bug notification because you are a member of
Attached debdiff for updating xenial to pulseaudio 1:8.0-0ubuntu3.3, in
order to address a few problems with Bluetooth audio (A2DP).
** Patch added: "xenial-a2dp-fixes-may2017.debdiff"
** Description changed:
[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
** Description changed:
- Bluetooth device doesn't play any sound in A2DP mode unless set to
- HSP/HFP first
+ [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.
- ---
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => In Progress
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
Confirmed on xenial, exactly how hife describes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582213
Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to
** Tags added: a2dp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
To manage notifications
I am experiencing the same problem, however, switching to HSP/HPF and
back will not work (when selecting A2DP from the dropdown menu in the
audio settings, the output sink switches to internal audio and when
reselecting bluetooth it is again in HSP/HPF mode). Only connecting as
HSP/HPF and then
32 matches
Mail list logo
