Dear Maintainer,

   * What led up to the situation?
        Connecting a plantronics B825-M only has the hsp/hfp sink usable in
audio configuration gui.
        a2db was selectable by gui but it still used hsp/hfp (check speaker
still has mono output).
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
        setfacl -m u:Debian-gdm:r /usr/bin/pulseaudio
        reboot

        This fixed the issue. It has no other effects as far I can see.

        TIA Lars

Hi,

Yes, the problem is that pulseaudio does not yield control of bluez
devices when the session stops being active. Merging with the existing
report.

Control: forcemerge 845938 848130

Thanks for confirming. I've merged the bugs.

Dear Maintainer,


   * What led up to the situation?

Dear Maintainer,

When connecting a bluetooth device that is capable of using the a2dp sink, pulseaudio
will only connect to it via hsp/hfp, and will not allow audio streaming to the
device.

Workaround:

Disconnect all bluetooth devices

insert 'load-module module-switch-on-connect' in to /etc/pulse/default.pa
(you only have to do this once)

Open a terminal and run the following commands, in order:
pulseaudio -k
pactl load-module module-bluetooth-discover
(you must run these commands manually after every reboot)

Re-connect bluetooth audio device with your favorite bluetooth device manager.

Confirm a2dp sink capibilities by running pavucontrol, selecting the "configuration"
tab, and ensuring that A2DP Sink is selected on the bluetooth audio device
that you want to use.

Finally, open your favorite music application and try playing some music as a
final test. The music should play in your bluetooth audio device.

There is a chance that your bluetooth audio device *may* connect properly,
but sound will still come from your speakers and NOT from your bluetooth audio device.
I have not found a proper workaround for this, other than to reboot and try again.

This bug has been around for a while on other linux distros, most notably
Ubuntu. See https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613
for additional information that could be helpful.

This is still an issue in Debian stretch: the gdm3 package runs
pulseaudio, which takes over the bluetooth device and makes it
impossible for regular users to connect to their bluetooth device
using the hifi A2DP sink. See #805414 for more details on that
side. There's a workaround for gdm3 (disabling the BT sink in gdm), so
I'll leave that aside for now and focus on the basic issue here.

From what I understand, the whole problem here is that PA doesn't
suspend the BT sink when it's not playing any sounds. Just like ALSA,
when no sound is playing, PA should give up the audio device and allow
other PA daemons to playback on the device. This is not a problem for
regular (ALSA) sound devices because that is correctly implemented
there.

Therefore, I would conclude that the underlying bug here is that PA
doesn't release the BT sink when not playing sound. There are many
bugs reported upstream regarding this issue, but the one I found the
most promising is this one:

https://bugs.freedesktop.org/show_bug.cgi?id=57167

... where an actual piece of code is outlined as being the culprit
here. There's another issue regarding BT sink sync that may be
relevant, although I'm not sure I understand the details here:

https://bugs.freedesktop.org/show_bug.cgi?id=45040

... it may be the other way around...

There is also a more generic upstrea bugs regarding this exact issue:

https://bugs.freedesktop.org/show_bug.cgi?id=92102

There are also 54 bluetooth-related bugs filed against pulseaudio
here, which I haven't thoroughly reviewed:

https://bugs.freedesktop.org/buglist.cgi?quicksearch=product%3APulseAudio%20bluetooth

So I'm not sure where to forward this, but it's certainly something
that should be fixed in pulseaudio, in my opinion.

A.

The problem is not limited to GDM, tho.

If you have several users logged in at the same time, only one of them
gets to use the bluetooth speaker, and once he gets it, the only way to
"free" the speaker (so another user can use it) seems to be to kill that
user's pulseaudio daemon.

The worst part is that the bluetooth speaker can easily get awarded to
a user who hasn't actually played any sound at all.

Currently, I work around this by manually removing bluetooth from the
pulseaudio config of all users except for the lucky one who is "more
deserving".  But it's a real PITA.


        Stefan

Greeting to you once again



I am writing for the second time as I did not receive any reply from you to
my previous message.



Kindly reply so we can discuss the subject as soon as possible.



Sincerely,



Andy Landman

Greeting to you once again



I am writing for the second time as I did not receive any reply from you to
my previous message.



Kindly reply so we can discuss the subject as soon as possible.



Sincerely,



Andy Landman

Hello,

Good morning,

We have gone through your samples from a partner and Here is our  Order
List. Please do bear in mind that we are very much in  need of this
order, quote your competitive prices.

Kindly send the Order confirmation.

Your early reply will be much appreciated.

Best Regards,

Maryanah Erwin.

PT FINDORA INTERNUSA

Jln Pahlawan 66 Kec. Arjawinangun

45162 CIREBON West-Java INDONESIA

tel : +62 231 357334

fax: +62 231 357260

email: marketing@findora.com

Hello,

Good morning,

We have gone through your samples from a partner and Here is our  Order
List. Please do bear in mind that we are very much in  need of this
order, quote your competitive prices.

Kindly send the Order confirmation.

Your early reply will be much appreciated.

Best Regards,

Maryanah Erwin.

PT FINDORA INTERNUSA

Jln Pahlawan 66 Kec. Arjawinangun

45162 CIREBON West-Java INDONESIA

tel : +62 231 357334

fax: +62 231 357260

email: marketing@findora.com