You are not logged in.
Got some bluetooth headphones that were operating fine on KDE Arch (standard Linux kernel). Tried to listen some music yesterday and even though I could pair with them just fine, there was no bluetooth output on the KDE sound applet.
Sound to other wired devices works just fine, as well as a microphone.
Any idea what to look for?
Offline
As a first guess, do the versions reported by uname -a and by pacman -Q linux (assuming you are using the stock kernel) match?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Look good AFAIK:
$ pacman -Q linux
linux 6.17.2.arch1-1
$ uname -a
Linux shocknawe 6.17.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 12 Oct 2025 12:45:18 +0000 x86_64 GNU/Linux
Also:
$ sudo dmesg |grep -i blue
[ 2.151608] usb 3-1.3: Product: Bluetooth Radio
[ 12.101551] Bluetooth: Core ver 2.22
[ 12.101566] NET: Registered PF_BLUETOOTH protocol family
[ 12.101568] Bluetooth: HCI device and connection manager initialized
[ 12.101573] Bluetooth: HCI socket layer initialized
[ 12.101576] Bluetooth: L2CAP socket layer initialized
[ 12.101580] Bluetooth: SCO socket layer initialized
[ 12.134536] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 12.135533] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 12.135536] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 12.136694] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 12.136743] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[ 12.285533] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[ 12.790611] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 12.790613] Bluetooth: BNEP filters: protocol multicast
[ 12.790616] Bluetooth: BNEP socket layer initialized
[ 12.791276] Bluetooth: MGMT ver 1.23
[ 93.588963] Bluetooth: RFCOMM TTY layer initialized
[ 93.588970] Bluetooth: RFCOMM socket layer initialized
[ 93.588974] Bluetooth: RFCOMM ver 1.11
[ 95.629026] Bluetooth: hci0: Opcode 0x0c24 failed: -110
[ 95.629032] Bluetooth: hci0: command 0x0c24 tx timeout
[ 95.629041] Bluetooth: hci0: Resetting usb device.
[ 97.677019] Bluetooth: hci0: command 0x0c24 tx timeout
[ 97.677021] Bluetooth: hci0: Opcode 0x2011 failed: -110
[ 97.677024] Bluetooth: hci0: Unable to add to allow list: -110
[ 97.677028] Bluetooth: hci0: Resetting usb device.
[ 99.725016] Bluetooth: hci0: Opcode 0x2041 failed: -110
[ 99.725023] Bluetooth: hci0: start background scanning failed: -110
[ 101.773009] Bluetooth: hci0: Opcode 0x0c24 failed: -110
[ 102.240573] Bluetooth: hci1: RTL: Failed to generate devcoredump
[ 102.242577] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
[ 102.447595] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 102.448583] Bluetooth: hci1: RTL: rom_version status=0 version=1
[ 102.448587] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 102.448749] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 102.448784] Bluetooth: hci1: RTL: cfg_sz 6, total sz 30210
[ 102.598577] Bluetooth: hci1: RTL: fw version 0xdfc6d922
[ 102.665731] Bluetooth: MGMT ver 1.23
$ lsmod |grep blue
bluetooth 1114112 46 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
rfkill 45056 5 bluetooth
From bluetoothctl, when I've paired the headphones:
[BLE_ATH-M50xBT]> info
Device 00:xx:xx:xx:xx:xx (public)
Name: BLE_ATH-M50xBT
Alias: BLE_ATH-M50xBT
Class: 0x00240418 (2360344)
Icon: audio-headphones
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Vendor specific (00001100-d102-11e1-9b23-00025b00a5a5)
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: Headset HS (00001131-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: Immediate Alert (00001802-0000-1000-8000-00805f9b34fb)
UUID: Link Loss (00001803-0000-1000-8000-00805f9b34fb)
UUID: Tx Power (00001804-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Heart Rate (0000180d-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v1000p0006d1003
Battery Percentage: 0x3e (62)
No errors in wireplumber, pipewire, pipewire-pulse.
Offline
might be related: https://bbs.archlinux.org/viewtopic.php … 3#p2267633
I have same issue: bluetooth connects, device appears and I can see sink but no sound coming out.
I do not use KDE though, I'm on hyprland with some remains of gnome-desktop from which I switched to hyprland.
Couple months back bluetooth worked just fine. I did not change any configuration, only thing I did consistently - `pacman -Suuy`.
I did not need bluetooth for the last several weeks so I'm not sure after what update it stopped to work.
I tried rolling back many packages: linux, bluez, linux-firmware, etc. Nothing helped.
My current versions (with rolled back bluez, linux & linux-firmware):
$ pacman -Q --info linux bluez pipewire wireplumber linux-firmware linux-firmware-intel | grep -B 1 Version
Name : linux
Version : 6.15.4.arch2-1
--
Name : bluez
Version : 5.80-1
--
Name : pipewire
Version : 1:1.4.9-1
--
Name : wireplumber
Version : 0.5.12-1
--
Name : linux-firmware
Version : 20250627-1
--
Name : linux-firmware-intel
Version : 20250627-1
After downgrading firmware, I did proper power-reset (with disconnecting from power socket) to force firmware refresh.
$ lsusb | grep -i blue
Bus 005 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth
in journal, I have following errors related to bluetooth:
- "Oct 17 12:42:31 WARP bluetoothd[1902]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down" - internet says this error can be ignored
- "Oct 17 12:47:22 WARP kernel: Bluetooth: hci0: Opcode 0x0401 failed: -16"
-
Oct 17 12:44:57 WARP bluetoothd[1902]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for A8:F5:E1:50:C8:18: Device or resource busy
Oct 17 12:44:58 WARP bluetoothd[1902]: profiles/audio/avctp.c:uinput_create() Can't open input device: No such file or directory (2)
Oct 17 12:44:58 WARP bluetoothd[1902]: profiles/audio/avctp.c:init_uinput() AVRCP: failed to init uinput for OpenRun Pro by Shokz
Oct 17 12:45:00 WARP bluetoothd[1902]: /org/bluez/hci0/dev_A8_F5_E1_50_C8_18/sep1/fd5: fd(41) ready
Oct 17 12:45:22 WARP kernel: Bluetooth: hci0: Opcode 0x0401 failed: -16
Oct 17 12:46:02 WARP wireplumber[19062]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_A8_F5_E1_50_C8_18/sep1/fd5
Oct 17 12:46:35 WARP bluetoothd[1902]: profiles/audio/avctp.c:uinput_create() Can't open input device: No such file or directory (2)
Oct 17 12:46:35 WARP bluetoothd[1902]: profiles/audio/avctp.c:init_uinput() AVRCP: failed to init uinput for OpenRun Pro by Shokz
Oct 17 12:46:38 WARP bluetoothd[1902]: /org/bluez/hci0/dev_A8_F5_E1_50_C8_18/sep1/fd7: fd(41) ready
Pipewire logs have:
Oct 17 07:55:26 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820540040 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:59 error:3 (Invalid argument)
Oct 17 07:55:26 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820540040 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:60 error:3 (Invalid argument)
Oct 17 07:59:26 WARP systemd[6388]: Stopping PipeWire Multimedia Service...
Oct 17 07:59:26 WARP /usr/lib/xdg-desktop-portal[8541]: Caught PipeWire error: connection error
Oct 17 07:59:26 WARP systemd[6388]: Stopped PipeWire Multimedia Service.
Oct 17 07:59:26 WARP systemd[6388]: pipewire.service: Consumed 13.307s CPU time, 26.8M memory peak.
Oct 17 07:59:26 WARP systemd[6388]: Closed PipeWire Multimedia System Sockets.
Oct 17 07:59:26 WARP systemd[6388]: Stopping PipeWire Multimedia System Sockets...
Oct 17 07:59:26 WARP systemd[6388]: Listening on PipeWire Multimedia System Sockets.
Oct 17 07:59:26 WARP systemd[6388]: Started PipeWire Multimedia Service.
Oct 17 07:59:27 WARP wireplumber[19062]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Oct 17 07:59:28 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820c1b8c0 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:92 error:3 (Invalid argument)
Oct 17 07:59:28 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820c1b8c0 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:93 error:3 (Invalid argument)
Oct 17 07:59:51 WARP pipewire[19060]: mod.rt: RTKit error: org.freedesktop.DBus.Error.NoReply
Oct 17 07:59:51 WARP pipewire[19060]: mod.rt: RTKit does not give us MaxRealtimePriority, using 1
Oct 17 08:00:16 WARP pipewire[19060]: mod.rt: RTKit error: org.freedesktop.DBus.Error.NoReply
Oct 17 08:00:16 WARP pipewire[19060]: mod.rt: RTKit does not give us MinNiceLevel, using 0
Oct 17 08:00:19 WARP pipewire[19060]: pw.node: (bluez_output.A8_F5_E1_50_C8_18.1-155) running -> error (Received error event)
Oct 17 08:00:41 WARP /usr/lib/xdg-desktop-portal[8541]: Failed connect to PipeWire: No node factory discovered
Oct 17 08:01:39 WARP pipewire[19060]: spa.audioconvert: 0x560e97c5ee10: (0 suppressed) out of buffers on port 0 2
Oct 17 08:01:39 WARP pipewire[19060]: spa.audioconvert: 0x560e97becd30: (0 suppressed) out of buffers on port 0 2
Oct 17 11:00:03 WARP pipewire[19060]: spa.audioconvert: 0x560e97c5ee10: (0 suppressed) out of buffers on port 0 2
Oct 17 11:00:03 WARP pipewire[19060]: spa.audioconvert: 0x560e97becd30: (0 suppressed) out of buffers on port 0 2
Oct 17 11:00:06 WARP pipewire[19060]: spa.audioconvert: 0x560e97c5ee10: (0 suppressed) out of buffers on port 0 2
Oct 17 11:00:06 WARP pipewire[19060]: spa.audioconvert: 0x560e97becd30: (0 suppressed) out of buffers on port 0 2
Oct 17 11:00:08 WARP pipewire[19060]: spa.audioconvert: 0x560e97c5ee10: (0 suppressed) out of buffers on port 0 2
Oct 17 11:00:08 WARP pipewire[19060]: spa.audioconvert: 0x560e97becd30: (0 suppressed) out of buffers on port 0 2
Oct 17 12:44:57 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820c1b8c0 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:700 error:3 (Invalid argument)
Oct 17 12:44:57 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820c1b8c0 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:701 error:3 (Invalid argument)
Oct 17 12:46:02 WARP pipewire[19060]: pw.node: (bluez_output.A8_F5_E1_50_C8_18.1-207) running -> error (Received error event)
Oct 17 12:46:35 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820c1b8c0 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:796 error:3 (Invalid argument)
Oct 17 12:46:35 WARP pipewire-pulse[6568]: mod.protocol-pulse: client 0x558820c1b8c0 [PulseAudio Volume Control]: ERROR command:104 (SEND_OBJECT_MESSAGE) tag:797 error:3 (Invalid argument)
Wireplumber
Oct 17 07:59:26 WARP wireplumber[19062]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
Oct 17 07:59:26 WARP wireplumber[19062]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
Oct 17 07:59:26 WARP wireplumber[19062]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
Oct 17 07:59:26 WARP wireplumber[19062]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
Oct 17 07:59:26 WARP wireplumber[19062]: wp-device: SPA handle 'api.alsa.acp.device' could not be loaded; is it installed?
Oct 17 07:59:26 WARP wireplumber[19062]: s-monitors: Failed to create 'api.alsa.acp.device' device
Oct 17 07:59:27 WARP wireplumber[19062]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Oct 17 07:59:27 WARP wireplumber[19062]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Oct 17 07:59:28 WARP wireplumber[19062]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+BTRH?
Oct 17 07:59:28 WARP wireplumber[19062]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+CSRSF=0,0,0,1,0,0,0
Oct 17 07:59:51 WARP wireplumber[19062]: mod.rt: RTKit error: org.freedesktop.DBus.Error.NoReply
Oct 17 07:59:51 WARP wireplumber[19062]: mod.rt: RTKit does not give us MaxRealtimePriority, using 1
Oct 17 08:00:16 WARP wireplumber[19062]: mod.rt: RTKit error: org.freedesktop.DBus.Error.NoReply
Oct 17 08:00:16 WARP wireplumber[19062]: mod.rt: RTKit does not give us MinNiceLevel, using 0
Oct 17 08:00:19 WARP wireplumber[19062]: spa.bluez5.sink.media: 0x7fa3e6470038: error 24
Oct 17 08:00:19 WARP wireplumber[19062]: pw.node: (bluez_output.A8_F5_E1_50_C8_18.1-155) running -> error (Received error event)
Oct 17 08:00:19 WARP wireplumber[19062]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_A8_F5_E1_50_C8_18/sep1/fd3
Oct 17 08:00:41 WARP wireplumber[19062]: wp-event-dispatcher: <WpAsyncEventHook:0x56285a489250> failed: <WpSiStandardLink:0x56285a93d7e0> link failed: some node was destroyed before the link was created
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get status for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: GLib: GError set over the top of a previous GError or uninitialized memory.
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get cgroup for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get cmdline for PID 456: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get status for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: GLib: GError set over the top of a previous GError or uninitialized memory.
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get cgroup for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get cmdline for PID 456: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get status for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: GLib: GError set over the top of a previous GError or uninitialized memory.
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get cgroup for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:01:46 WARP wireplumber[19062]: wp-proc-utils: failed to get cmdline for PID 456: No such file or directory
Oct 17 08:02:09 WARP wireplumber[19062]: wp-proc-utils: failed to get status for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:02:09 WARP wireplumber[19062]: GLib: GError set over the top of a previous GError or uninitialized memory.
Oct 17 08:02:09 WARP wireplumber[19062]: wp-proc-utils: failed to get cgroup for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:02:09 WARP wireplumber[19062]: wp-proc-utils: failed to get cmdline for PID 456: No such file or directory
Oct 17 08:02:10 WARP wireplumber[19062]: wp-proc-utils: failed to get status for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:02:10 WARP wireplumber[19062]: GLib: GError set over the top of a previous GError or uninitialized memory.
Oct 17 08:02:10 WARP wireplumber[19062]: wp-proc-utils: failed to get cgroup for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:02:10 WARP wireplumber[19062]: wp-proc-utils: failed to get cmdline for PID 456: No such file or directory
Oct 17 08:02:10 WARP wireplumber[19062]: wp-proc-utils: failed to get status for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:02:10 WARP wireplumber[19062]: GLib: GError set over the top of a previous GError or uninitialized memory.
Oct 17 08:02:10 WARP wireplumber[19062]: wp-proc-utils: failed to get cgroup for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:02:10 WARP wireplumber[19062]: wp-proc-utils: failed to get cmdline for PID 456: No such file or directory
Oct 17 08:04:11 WARP wireplumber[19062]: wp-proc-utils: failed to get status for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:04:11 WARP wireplumber[19062]: GLib: GError set over the top of a previous GError or uninitialized memory.
Oct 17 08:04:11 WARP wireplumber[19062]: wp-proc-utils: failed to get cgroup for PID 456: Failed to open file “/proc/456/status”: No such file or directory
Oct 17 08:04:11 WARP wireplumber[19062]: wp-proc-utils: failed to get cmdline for PID 456: No such file or directory
Oct 17 12:44:55 WARP wireplumber[19062]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+BTRH?
Oct 17 12:44:56 WARP wireplumber[19062]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+CSRSF=0,0,0,1,0,0,0
Oct 17 12:46:02 WARP wireplumber[19062]: pw.node: (bluez_output.A8_F5_E1_50_C8_18.1-207) running -> error (Received error event)
Oct 17 12:46:02 WARP wireplumber[19062]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_A8_F5_E1_50_C8_18/sep1/fd5
Oct 17 12:46:35 WARP wireplumber[19062]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+BTRH?
Oct 17 12:46:35 WARP wireplumber[19062]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+CSRSF=0,0,0,1,0,0,0
I'm so lost
Last edited by axp (Yesterday 17:05:17)
Offline
Seems to be a recent issue. Checking my pacman log:
# less pacman.log |grep bluez
[2025-08-31T19:36:04+0300] [ALPM] installed bluez-libs (5.83-1)
[2025-09-02T14:55:59+0300] [PACMAN] Running 'pacman -Suy bluez bluez-utils'
[2025-09-02T14:56:02+0300] [ALPM] installed bluez (5.83-1)
[2025-09-02T14:56:02+0300] [ALPM] installed bluez-utils (5.83-1)
[2025-09-02T18:44:54+0300] [ALPM] installed bluez-qt (6.17.0-1)
[2025-09-14T19:10:44+0300] [ALPM] upgraded bluez-qt (6.17.0-1 -> 6.18.0-1)
[2025-09-21T14:36:18+0300] [ALPM] upgraded bluez (5.83-1 -> 5.84-1)
[2025-09-21T14:36:18+0300] [ALPM] upgraded bluez-libs (5.83-1 -> 5.84-1)
[2025-09-21T14:36:18+0300] [ALPM] upgraded bluez-utils (5.83-1 -> 5.84-1)
[2025-09-23T16:24:19+0300] [PACMAN] Running 'pacman -Syu pulseaudio-bluetooth bluez-obex'
[2025-09-23T16:24:35+0300] [PACMAN] Running 'pacman -Syu bluez-obex'
[2025-09-23T16:24:41+0300] [ALPM] installed bluez-obex (5.84-1)
[2025-10-15T12:39:54+0300] [ALPM] upgraded bluez-qt (6.18.0-1 -> 6.19.0-1)
This is a new arch installation (couple of months). It did work in September. Something to do with the bluez-qt upgrade? Wish we could correlate the date the issue started with the upgrades done. Unfortunately I mostly use wired headphones, so I can not tell when the issue actually appeared.
Offline
Found out that replacing wireplumber with pipewire-media-session makes bluetooth work.
Though rolling back wireplumber to 0.5.11-1 did not help
Offline