After recent updates, a bluetooth speaker is no longer available

tumbleweed v20231005
Bose Mini II SoundLink

After an update from about 2 weeks ago, the Bose speaker is no longer recognized as a sound device. It connects to the computer via Bluetooth just fine.

Any suggestions?

This is the only log information I can find. The messages are too cryptic.

2023-10-11T12:36:12-0700 sma-station14l bluetoothd[1650]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
2023-10-11T12:36:12-0700 sma-station14l dbus-daemon[1651]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.125" (uid=1000 pid=4261 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=1650 comm="/usr/libexec/bluetooth/bluetoothd")
2023-10-11T12:36:12-0700 sma-station14l audio-recorder[3949]: g_object_get_is_valid_property: object class 'GstPipeWireSink' has no property named 'device'
2023-10-11T12:36:20-0700 sma-station14l wireplumber[4261]: RFCOMM receive command but modem not available: AT+BTRH?
2023-10-11T12:36:20-0700 sma-station14l audio-recorder[3949]: g_object_get_is_valid_property: object class 'GstPipeWireSink' has no property named 'device'
2023-10-11T12:36:20-0700 sma-station14l audio-recorder[3949]: g_object_get_is_valid_property: object class 'GstPipeWireSink' has no property named 'device'
2023-10-11T12:36:23-0700 sma-station14l wireplumber[4261]: RFCOMM receive command but modem not available: AT+CSRSF=0,0,0,1,0,0,0
2023-10-11T12:36:23-0700 sma-station14l bluetoothd[1650]: profiles/audio/avctp.c:avctp_control_confirm() Control: Refusing unexpected connect
2023-10-11T12:36:23-0700 sma-station14l kernel: input: Bose Mini II SoundLink (AVRCP) as /devices/virtual/input/input30
2023-10-11T12:36:23-0700 sma-station14l systemd-logind[1829]: Watching system buttons on /dev/input/event18 (Bose Mini II SoundLink (AVRCP))

As suggested in another “bluetooth” thread in here recently, the 20231008 snapshot update has bluetooth updates and a couple of folks in that thread confirmed they’re working now.

Update to that version and check. (there’s another update today, too)

https://forums.opensuse.org/t/bluetooth-no-longer-starting-at-boot/169758/8

Well, no. Bluetooth starts as it should, and connects to the Bose speaker. It is that the Bluetooth device is no longer recognized as a sound device.

tumbleweed v20231012

FWIW, I found a similar problem describing a “Bose Mini II SoundLink” device (in a Mac OS environment). The device would pair ok, but not seen as a sound device. It may be relevant to your situation…

https://kevinmatsunaga.com/no-sound-with-paired-bose-mini-ii-soundlink/

After spending nearly 24 hours on this fix, I finally found one on the Bose website. It was clear as daylight. You needed to reset your Bose speaker by holding the Power button for roughly 10 seconds or until the lights all turn off. You can then re-pair on your Macbook Pro and your speaker will pop up in Sound Preferences.

Worth a shot anyway.

Thank you. Alas, that made no difference.
The same list of log entries occurred as shown in the first post.

Ok, a bug report is probably the best way forward.

Anything interesting returned from the following command?

sudo journalctl -b | egrep -i "blue|firm"

Anything interesting returned from the following command?

sudo journalctl -b | egrep -i "blue|firm"

Is this interesting?

Oct 14 20:55:47 sma-station14l dbus-daemon[1653]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.129" (uid=1000 pid=11049 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=1652 comm="/usr/libexec/bluetooth/bluetoothd")
Oct 14 20:55:48 sma-station14l bluetoothd[1652]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Oct 14 20:56:17 sma-station14l bluetoothd[1652]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Oct 14 20:56:20 sma-station14l bluetoothd[1652]: src/service.c:btd_service_connect() avrcp-controller profile connect failed for 08:DF:1F:43:AD:9B: Operation already in progress
Oct 14 20:56:39 sma-station14l bluetoothd[1652]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Oct 14 20:56:39 sma-station14l dbus-daemon[1653]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.129" (uid=1000 pid=11049 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=1652 comm="/usr/libexec/bluetooth/bluetoothd")
Oct 14 20:57:01 sma-station14l bluetoothd[1652]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 08:DF:1F:43:AD:9B: Invalid exchange (52)
Oct 14 20:57:01 sma-station14l bluetoothd[1652]: src/service.c:btd_service_connect() Hands-Free Voice gateway profile connect failed for 08:DF:1F:43:AD:9B: Cannot allocate memory
Oct 14 20:57:13 sma-station14l bluetoothd[1652]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 08:DF:1F:43:AD:9B: Connection refused (111)
Oct 14 20:57:13 sma-station14l bluetoothd[1652]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 08:DF:1F:43:AD:9B: Connection refused (111)
Oct 14 20:57:37 sma-station14l bluetoothd[1652]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 08:DF:1F:43:AD:9B: Connection refused (111)
Oct 14 20:57:37 sma-station14l bluetoothd[1652]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 08:DF:1F:43:AD:9B: Connection refused (111)

Thanks for sharing this output. See if the advice in this thread helps.

It would seem I have been unclear about the issue the system is experiencing.

There is no problem with bluetooth connecting to the sound device, Bose Mini II Soundlink.
The issue is that the speaker is no longer recognized as a valid sound output device.

I notice there is a new daemon: Wireplumber. I do not recall seeing that until recently. Is it a replacement for some other service?

I’m aware of what you stated. Can you confirm this via output from bluetoothctl command?

Wireplumber is a session and policy manager for pipewire. It replaced ‘pipewire-media-session’ months ago.

More reading:
https://wiki.archlinux.org/title/WirePlumber
https://fedoramagazine.org/wireplumber-the-new-pipewire-session-manager/

Without arguments: sudo bluetoothectl

hci0 new_settings: powered bondable ssp br/edr le secure-conn 
Agent registered
[CHG] Controller 00:1A:7D:DA:71:13 Pairable: yes
[Bose Mini II SoundLink]# 

A few more random commands:

[Bose Mini II SoundLink]# list
Controller 00:1A:7D:DA:71:13 sma-station14l [default]
[Bose Mini II SoundLink]# devices
Device 08:DF:1F:43:AD:9B Bose Mini II SoundLink
[Bose Mini II SoundLink]# export
SHELL=0x5652ac751a70
HISTORY=0x5652ac3ba0f0
DBUS_CONNECTION=0x5652ac829dd0
/org/bluez/hci0=0x5652ac833290
/org/bluez/hci0/dev_08_DF_1F_43_AD_9B=0x5652ac842e10
[Bose Mini II SoundLink]# version
Version 5.69

…and if you attempt to pair?

bluetoothctl pair 08:DF:1F:43:AD:9B
Attempting to pair with 08:DF:1F:43:AD:9B
Failed to pair: org.bluez.Error.AlreadyExists

If you disconnect it first then pair?

Browsing the link you offered, I tried this:

 wpctl status
PipeWire 'pipewire-0' [0.3.80, jmoe@sma-station14l, cookie:3754583617]
 └─ Clients:
        31. gnome-shell                         [0.3.80, jmoe@sma-station14l, pid:10453]
        32. WirePlumber                         [0.3.80, jmoe@sma-station14l, pid:11049]
        33. WirePlumber [export]                [0.3.80, jmoe@sma-station14l, pid:11049]
        36. audio-recorder                      [0.3.80, jmoe@sma-station14l, pid:10753]
        43. xdg-desktop-portal                  [0.3.80, jmoe@sma-station14l, pid:11162]
        44. wpctl                               [0.3.80, jmoe@sma-station14l, pid:16396]

Audio
 ├─ Devices:
 │      37. Bose Mini II SoundLink              [bluez5]
 │  
 ├─ Sinks:
 │  *   38. Bose Mini II SoundLink              [vol: 0.50]
 │  
 ├─ Sink endpoints:
 │  
 ├─ Sources:
 │  
 ├─ Source endpoints:
 │  
 └─ Streams:

Then this:

 wpctl inspect 38
id 38, type PipeWire:Interface:Node
    api.bluez5.address = "08:DF:1F:43:AD:9B"
    api.bluez5.codec = "sbc"
    api.bluez5.profile = "a2dp-sink"
    api.bluez5.transport = ""
    audio.adapt.follower = ""
    card.profile.device = "1"
  * client.id = "33"
    clock.quantum-limit = "8192"
    device.api = "bluez5"
  * device.id = "37"
    device.routes = "1"
  * factory.id = "8"
    factory.mode = "merge"
    factory.name = "api.bluez5.a2dp.sink"
    library.name = "audioconvert/libspa-audioconvert"
  * media.class = "Audio/Sink"
    media.name = "Bose Mini II SoundLink"
  * node.description = "Bose Mini II SoundLink"
    node.driver = "true"
  * node.name = "bluez_output.08_DF_1F_43_AD_9B.1"
    node.pause-on-idle = "false"
  * object.serial = "57"
  * priority.driver = "1010"
  * priority.session = "1010"

Which leads me to suspect that Gnome Desktop may be the problem. Gnome lists 4 available sound devices. The Bose is the only one missing.

I note that “wireplumber-audio” module is not installed. Doing so would de-install several pulseaudio modules. I am reluctant to randomly replace software.

Ok, I’m using openSUSE Leap 15.5 and have the following wireplumber packages installed

~> rpm -qa |grep wireplumber
wireplumber-lang-0.4.13-150500.1.2.noarch
wireplumber-audio-0.4.13-150500.1.2.noarch
wireplumber-0.4.13-150500.1.2.x86_64
libwireplumber-0_4-0-0.4.13-150500.1.2.x86_64

Let’s see what others suggest.

Actually, I was surprised that you still have pulseaudio installed. Most desktop users are using the pipewire framework now. You can install ‘pipewire-pulseaudio’ for compatibility purposes if desired.

Okay, I replaced pulseaudio with wireplumber. I had to boot, and the bluetooth speaker is now an option.

SOLVED!