debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #00624
[Bug 2111586] Re: Redmi Buds 5 Bluetooth earbuds connect successfully but do not appear as an audio device in Ubuntu 24.04 (PipeWire/WirePlumber/BlueZ), while other Bluetooth headsets work as expected.
bluez/noble-updates,now 5.72-0ubuntu5.1 amd64 [installed,automatic]
pipewire/noble-updates,now 1.0.5-1ubuntu3 amd64 [installed,automatic]
wireplumber/noble,now 0.4.17-1ubuntu4 amd64 [installed]
Device 48:73:CB:62:BB:DE (public)
Name: Redmi Buds 5 Pro
Alias: Redmi Buds 5 Pro
Appearance: 0x0941 (2369)
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific (00000000-0000-0000-0099-aabbccddeeff)
UUID: Vendor specific (00000000-deca-fade-deca-deafdecacaff)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Audio Input Control (00001843-0000-1000-8000-00805f9b34fb)
UUID: Volume Control (00001844-0000-1000-8000-00805f9b34fb)
UUID: Volume Offset Control (00001845-0000-1000-8000-00805f9b34fb)
UUID: Coordinated Set Identif.. (00001846-0000-1000-8000-00805f9b34fb)
UUID: Microphone Control (0000184d-0000-1000-8000-00805f9b34fb)
UUID: Audio Stream Control (0000184e-0000-1000-8000-00805f9b34fb)
UUID: Broadcast Audio Scan (0000184f-0000-1000-8000-00805f9b34fb)
UUID: Published Audio Capabil.. (00001850-0000-1000-8000-00805f9b34fb)
UUID: Common Audio (00001853-0000-1000-8000-00805f9b34fb)
UUID: Telephony and Media Audio (00001855-0000-1000-8000-00805f9b34fb)
UUID: Unknown (0000af00-0000-1000-8000-00805f9b34fb)
UUID: Unknown (0000fd2d-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (0000ff01-0000-1000-8000-00805f9b34ff)
UUID: Vendor specific (5052494d-2dab-0341-6972-6f6861424c45)
UUID: Vendor specific (5052494d-2dab-0741-6972-6f6861424c45)
UUID: Vendor specific (df21fe2c-2515-4fdb-8886-f12c4d67927c)
Modalias: usb:v1915pEEEEd0001
ManufacturerData.Key: 0xff00 (65280)
ManufacturerData.Value:
00 de bb 62 cb 73 48 ...b.sH
ServiceData.0000184e-0000-1000-8000-00805f9b34fb:
00 ff 0f 43 02 00 ...C..
ServiceData.00001855-0000-1000-8000-00805f9b34fb:
2a 00 *.
ServiceData.00001853-0000-1000-8000-00805f9b34fb:
00
--
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/2111586
Title:
Redmi Buds 5 Bluetooth earbuds connect successfully but do not appear
as an audio device in Ubuntu 24.04 (PipeWire/WirePlumber/BlueZ), while
other Bluetooth headsets work as expected.
Status in pipewire package in Ubuntu:
New
Bug description:
Description:
Ubuntu release: Ubuntu 24.04.2 LTS (GNOME 46, X11)
Kernel version: Linux 6.11.0-26-generic
Hardware: Lenovo Legion 5 15ACH6H, AMD Ryzen 5 5600H, NVIDIA RTX 3060, 16GB RAM
PipeWire version: 1.0.5-1ubuntu3
WirePlumber version: 0.4.17-1ubuntu4
BlueZ version: 5.72-0ubuntu5.1
What I expected to happen:
When connecting my Redmi Buds 5 Bluetooth earbuds, I expected them to appear as an audio device (bluez_card) and be available for audio output, as they did previously on this system.
What happened instead:
The Redmi Buds 5 connect via Bluetooth and show as connected, but do not appear as an audio device (no bluez_card in pactl list short cards), so they cannot be used for audio. Other Bluetooth headsets (e.g., Soundcore) work as expected and appear as audio devices.
Additional information:
The issue started recently; the earbuds worked previously on Ubuntu 24.04.
All relevant packages are up to date.
I have tried removing configs, reinstalling packages, and using both bluetoothctl and the GNOME GUI to connect.
The earbuds work fine on other devices (e.g., Android phone).
Logs and further details can be provided if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2111586/+subscriptions
References