Bluetooth not Working After Update

English Network/Internet
1

TW/Gnome

This last update skewered Bluetooth. Bluetooth always worked fine. As of now, Bluetooth shows a connection to the bluetooth speaker, the bluetooth speaker reports a connection, but the sound still only comes through the laptop. When I go to Settings/Sound, the only option is internal speakers.

I found this solution for plasma users: Execute rm ~/.config/bluedevilglobalrc

Is there an equivalent for Gnome?

For what it’s worth, I tried rolling back but the update was too large. Snapper chokes up on my Surface. (That’s a first.)

2

“what” TW snapshot version are you at?

Folks at 20231005 complained about Bluetooth … the 20231008 snapshot update has Bluetooth fixes, which worked for some. There’s also a 20231010 update that happened today (nothing Bluetooth that I saw)

3

Hi,
I’m on GNOME Wayland Tumbleweed snapshot 20231010.
Bluetooth works fine here.

bandithijo@opensuse ~]$ bluetoothctl 
Agent registered
hci0 new_settings: powered bondable ssp br/edr le secure-conn 
[CHG] Controller E4:A4:71:E7:A5:6C Pairable: yes
AdvertisementMonitor path registered
[OpenComm by Shokz]#

The OpenComm by Shokz is the Bluetooth device that connected.
I hope this small piece of information can help you.

4

Inxi reports: openSUSE Tumbleweed 20231010

5

Interesting, running the same command I get:

Agent registered
[CHG] Controller D8:C4:97:C6:0E:67 Pairable: yes
[LE-Bose Revolve+ SoundLink]#

But the sound is coming from the laptop. Wonder if there’s something screwy with pulseaudio?

6

It looks perfect!

Maybe, you only need to switch “audio output source” from GNOME Settings > Sound. Then, On “Ouput Device”, select your device that wants to audio out.

Screenshot_2023-10-12_09-19-34
Screenshot_2023-10-12_09-19-341114×850 75.1 KB

As far as I know, for audio server, we do not use PulseAudio anymore, we have moved into Pipewire as audio server and Wireplumber as media session manager.

I hope this small piece of information can help you.

7

Thanks, but that’s the weird thing. The bluetooth speaker doesn’t show up under Output Device. That’s what makes me wonder if it’s a ̶pu̶l̶s̶e̶a̶u̶d̶i̶o̶ pipewire problem…

9

Oh I see.
I’ve been in situation like this with “PipeWire thing” a few times.

When I suffer from audio server problem, in this case, PipeWire thing, I usually run the “1st procedure from audio first aid kit” (that I call it) to handle it.

systemctl --user restart pipewire.service
systemctl --user restart wireplumber.service

Or, if you use Bash shell (default shell) you can join those 2 command like this

systemctl --user restart {pipewire,wireplumber}.service

Those commands are not a “dangerous” command. Maybe you want to consider to try.

I have documented those in my blog (Bahasa). [1]

I hope this small piece of information can help you.

[1] Restart Pipewire Tanpa Perlu Logout | BanditHijo.dev

10

Thanks! I’ll try that in the morning and report back. :slight_smile:

1 Like
11

I’m on Leap 15.5, so my experience might not be relevant.

I have bluetooth headphones, and on reboot they do not show up as an output device. I have to use (as root):

systemctl restart bluetooth

and after that they show up (until I reboot).

1 Like
12

I tried your solution first (restarting bluetooth) and it worked.

1.) Issued command: systemctl restart bluetooth
2.) Restarted bluetooth speaker
3.) Bluetooth speaker connected and showed up in Sound Settings.

Kind of a brute force solution but maybe a future update will fix this? I’ll also try restarting pipewire with the next restart of TW.

1 Like
13

The bluetooth bug hasn’t gone away with updates—yet—but restarting bluetooth works every time.

I’ve done this before (not often enough to remember without a lot of Googling) but isn’t there a simple place to run a root command at startup? For instance:

sleep 30 && sudo systemctl restart bluetooth
14

I’ll describe my experience. However, this was with Leap rather than with Tumbleweed.

I was finding that I needed:

systemctl restart bluetooth

after each boot – and, indeed, after a logout/login.

I have Plasma configured to start from a saved session.

I have recently re-saved my session. And, after that, bluetooth just works normally.

When I originally saved a session, this was before I had even paired my bluetooth headphones. When I most recently saved my session, this was with the headphones paired and connected. It looks as if that makes a difference.

15

I’m unfortunately having the same or similar issue, but not just limited to audio devices.
I can pair a new bluettoth mouse successfully, but it will not move the pointer until I restart bluetooth.
Bluetoth was working fine in the past, sometime this year this weird issue started and until today it is not resolved for me.
Did anything change for you? Is it working normally on your machine by now?

PS: I’m on Tumbleweed with latest updates.