AnswerBun.com

Bluetooth speaker connected but not listed in sound output

Ask Ubuntu Asked by Subhadip Roy on December 29, 2021

I can successfully connect a Mi BlueTooth speaker to Ubuntu, but I cannot play sound through it, because it is not listed in my sound output list.

Bluetooth module for PulseAudio sound server

Is present on my system, however running sudo pactl load-module module-bluetooth-discover returns:

Failure: Module initialization failed. 

How can I solve this issue?
`

8 Answers

I didn't have any luck with /var/lib/gdm3/.config/pulse/client.conf or /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket or /var/lib/gdm3/.config/pulse/default.pa - I kept seeing Debian-gdm's pulseaudio process. What worked for me was the link from https://wiki.debian.org/BluetoothUser/a2dp#Refused_to_switch_profile_to_a2dp_sink:_Not_connected to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845938 and the removal of execute permission from the Debian-gdm user to pulseaudio in the original submission there, which I refined as follows to avoid the reboot:

sudo setfacl -m u:Debian-gdm:r /usr/bin/pulseaudio
sudo killall pulseaudio

...

Well, that's remained working for me across upgrades and reboots - I only see a pulseaudio process in my username - but I still had problems today getting my Amazon Echo to connect as a sink rather than a source. What finally worked (today) was initiating the pairing as a sink from the blueman-manager program from the blueman package.

Answered by Martin Dorey on December 29, 2021

I followed the Debian documentation troubleshooting help for A2DP ("Advanced Audio Distribution Profile") that works for me:

In order to prevent GDM from capturing the A2DP sink on session start, edit /var/lib/gdm3/.config/pulse/client.conf (or create it, if it doesn't exist):

autospawn = no
daemon-binary = /bin/true

After that you have to grant access to this file to Debian-gdm user:

chown Debian-gdm:Debian-gdm /var/lib/gdm3/.config/pulse/client.conf

You will also need to disable pulseaudio startup:

rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket

In order to auto-connect a2dp for some devices, add this to /etc/pulse/default.pa:

load-module module-switch-on-connect

Reboot.

Now the sound device (bluetooth headset) should be accessible through pavucontrol > and standard audio device manager.

Answered by Genjo on December 29, 2021

I had a lot of trouble getting my No Bounds speaker to connect. Clicking the Bluetooth icon in the taskbar showed 3 devices called 'No Bounds'. The first one would connect, then disconnect in 10 secs. So I decided to delete the device. Then when I turned on the No Bounds, it connected! Now works perfectly (LM19.1)

Answered by David on December 29, 2021

This is old, but I had the same problem on 18.04 and none of the solutions offered worked for me.

What worked for me, at least for Audacious, was to start PulseAudio Volume Control, and after I started Audacious - I selected Mi Bluetooth Computer Speaker from the dropdown.

PulseAudio Volume Control Playback tab

Answered by Jomu on December 29, 2021

For me the easiest and right solution to that was:

sudo apt install pulseaudio-module-bluetooth 

then i removed the device from the bluetooth known devices, reboot and all worked. I can now see the headphones as sound output in sound settings. Hope it helps!

Answered by fthinker on December 29, 2021

I had to use Lou Gro's blueman solution every time I rebooted. This fixed it for me:

https://wiki.archlinux.org/index.php/Bluetooth_headset#Gnome_with_GDM

Follow the instructions under "Gnome with GDM" (use gdm3 in the paths instead of gdm for Gnome 3)

Answered by Roger on December 29, 2021

This is what is working for me for Bose QuietComfort 35 on Ubuntu 16.04. pauvcontrol didn't do it for me, and neither did the numerous settings changes and module loadings recommended elsewhere. So give this a try:

  1. Install blueman

    sudo apt install blueman
    
  2. Delete the paired device in the bluetooth settings.

  3. Run these commands in terminal:

    $ sudo pkill pulseaudio
    $ sudo /etc/init.d/bluetooth restart
    
  4. Turn off headphones.

  5. Turn on headphones, and press green/go until headphones notification voice says "Ready to pair."

  6. Launch blueman, and from the upper right menu, right-click the icon to bring up the blueman menu. Select Setup new device.

  7. Pair the device, and when you are given an option, not Headphones, not Handsfree. Use the Audio sink option.

  8. Then when you look into the audio settings panel, the device should be displayed.

Answered by Lou Gro on December 29, 2021

One way to solve the problem is to:

  1. unpair the device
  2. run the following command on terminal: sudo pkill pulseaudio
  3. and then pair again the speaker via bluetooth.

The speaker is now displayed on the output audio list, which needs to selected for obtaining output sound.

Remember to, under Sound Settings, change Mode to High Fidelity Playback (A2DP Sink).

Answered by Subhadip Roy on December 29, 2021

Add your own answers!

Related Questions

systemctl –state=failed

0  Asked on December 5, 2021 by tomasz-groch

 

Systemctl failure using –global setting

1  Asked on December 5, 2021 by mark-knittel

   

Ubuntu 20.04 – Failed to start GNOME Shell on X11

0  Asked on December 4, 2021 by facundo-flores

       

Google (maybe the browser?) not recognizing USB webcam

0  Asked on December 4, 2021 by tkbegemot

         

How to do a clean reinstall of ubuntu?

2  Asked on December 3, 2021 by mahiro

 

Cannot delete print job on Ubuntu 18.04

1  Asked on December 3, 2021 by manfred-steiner

 

Postfix is not logging anything to journal

1  Asked on December 3, 2021 by r4ptor

     

systemctl enable fprintd.service fails

1  Asked on December 3, 2021 by randy-broman

   

Recovering a lost user group

1  Asked on December 3, 2021

 

Ask a Question

Get help from others!

© 2023 AnswerBun.com. All rights reserved. Sites we Love: PCI Database, MenuIva, UKBizDB, Menu Kuliner, Sharing RPP, SolveDir