You are not logged in.
On an AMD Framework 13 with MEDIATEK MT7922 wireless card and Pipewire, and Bluetooth audio support is pretty much completely nonfunctional for me. When trying to pair a remembered device, journalctl shows these lines:
Oct 31 18:25:51 lithium kernel: Bluetooth: hci0: ACL packet for unknown connection handle 3837
Oct 31 18:25:52 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-48 noise=9999 txrate=720600
Oct 31 18:25:55 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-43 noise=9999 txrate=720600
Oct 31 18:25:58 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=720600
Oct 31 18:26:01 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-45 noise=9999 txrate=576400
Oct 31 18:26:04 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-50 noise=9999 txrate=720600
Oct 31 18:26:07 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=9999 txrate=720600
Oct 31 18:26:10 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=9999 txrate=720600
Oct 31 18:26:13 lithium rtkit-daemon[912]: Supervising 8 threads of 5 processes of 1 users.
Oct 31 18:26:13 lithium rtkit-daemon[912]: Supervising 8 threads of 5 processes of 1 users.
Oct 31 18:26:13 lithium rtkit-daemon[912]: Successfully made thread 11133 of process 10502 owned by '1000' RT at priority 10.
Oct 31 18:26:13 lithium rtkit-daemon[912]: Supervising 9 threads of 6 processes of 1 users.
Oct 31 18:26:13 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-50 noise=9999 txrate=720600
Oct 31 18:26:15 lithium rtkit-daemon[912]: Supervising 9 threads of 6 processes of 1 users.
Oct 31 18:26:15 lithium rtkit-daemon[912]: Supervising 9 threads of 6 processes of 1 users.
Oct 31 18:26:16 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-50 noise=9999 txrate=720600
Oct 31 18:26:19 lithium bluetoothd[588]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110)
Oct 31 18:26:19 lithium wireplumber[906]: spa.bluez5: Acquire /org/bluez/hci0/dev_41_42_C7_38_C1_C0/sep2/fd2 returned error: org.bluez.Error.Failed
Oct 31 18:26:19 lithium wireplumber[906]: pw.node: (bluez_output.41_42_C7_38_C1_C0.1-86) running -> error (Received error event)
Oct 31 18:26:19 lithium wireplumber[906]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_41_42_C7_38_C1_C0/sep2/fd2
Oct 31 18:26:19 lithium pipewire[905]: pw.node: (bluez_output.41_42_C7_38_C1_C0.1-86) idle -> error (Received error event)
Oct 31 18:26:19 lithium wpa_supplicant[683]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-52 noise=9999 txrate=720600
Oct 31 18:26:21 lithium bluetoothd[588]: profiles/audio/avdtp.c:cancel_request() Abort: Connection timed out (110)
Oct 31 18:26:21 lithium kded6[1038]: org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium kdeconnectd[1422]: 2024-10-31T18:26:21 org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium plasmashell[1126]: org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium plasmashell[1126]: org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium bluetoothd[588]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Oct 31 18:26:21 lithium kded6[1038]: org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium kdeconnectd[1422]: 2024-10-31T18:26:21 org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium kded6[1038]: org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium kded6[1038]: org.kde.pulseaudio: No object for name "bluez_input.41:42:C7:38:C1:C0"
Oct 31 18:26:21 lithium kdeconnectd[1422]: 2024-10-31T18:26:21 org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:21 lithium kdeconnectd[1422]: 2024-10-31T18:26:21 org.kde.pulseaudio: No object for name "bluez_input.41:42:C7:38:C1:C0"
Oct 31 18:26:22 lithium plasmashell[1126]: org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:22 lithium plasmashell[1126]: org.kde.pulseaudio: No object for name "bluez_output.41_42_C7_38_C1_C0.1"
Oct 31 18:26:22 lithium plasmashell[1126]: org.kde.pulseaudio: No object for name "bluez_input.41:42:C7:38:C1:C0"
The device connects for a second or two, but audio doesn't work during that time and it disconnects right after. The only way I've found to get this device to work again is to remove it and reconnect through bluetoothctl, but that's a massive PITA I'd rather not deal with whenever I want to listen to music.
I heard some talk of Bluetooth issues on 6.11.3/4, but nothing exactly like what I'm dealing with here. Any help would be very much appreciated.
Offline
same Issue best option is to change the kernal to linux-lts or update the system
Offline
Did you already have a chance to test if the 6.11.6 stable kernel fixes the issue for you? Additionally, could you try if the latest linux-mainline release fixes it?
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-6.12rc5-1-x86_64.pkg.tar.zst
Offline
Just tested, neither fixes this issue. I can try looking at earlier kernels to pinpoint what happened, if that would help.
Offline
Yeah what was the last version that was working? Could you try version 6.10 for example? You can install it from the Arch Linux Archive:
sudo pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.10.9.arch1-1-x86_64.pkg.tar.zst
Offline
I traced it back to 6.9.1 before giving up, since I know Bluetooth audio was working well after 6.10. This may be an issue with another component of the Bluetooth/Pipewire stack entirely; firmware maybe? I'll see if downgrading linux-firmware helps, but I'm pretty sure this isn't a kernel bug after all.
Offline
Downgraded a couple packages, and narrowed the problem down to bluez. Restarting it seems to have fixed the issue, though I'm not sure how.
Last edited by ctrlaltmilk (2024-11-05 09:26:04)
Offline
There was an update to bluez a few days ago, likely containing a fix but you hadn't restartet it yet?
Offline