You are not logged in.
Pages: 1
Topic closed
Hello, I face an issue with my external bluetooth speaker after an update from last week. When trying to connect, it hangs for a few seconds and then the device powers off itself.
I also have a bluetooth headset but this one is still connecting as expected.
I'm on Linux Kernel 6.9.5-arch1-1 now but I also had the issue with the previous version. I have the last LTS version installed and all is working fine when booting with the LTS so I imagine it's linked to the kernel.
I tried un-pairing and re-pairing the device, as I saw that sometimes it can solve connection issues but it did not change anything: speakers can't connect but headset is ok.
Here are the corresponding lines from journalctl
journalctl -p 3 -b
juin 19 10:37:36 hal pipewire-pulse[1561]: mod.protocol-pulse: 0x64e39af0f110: card 103 port 0 profiles inconsistent (1 < 2)
juin 19 10:37:36 hal pipewire-pulse[1561]: mod.protocol-pulse: 0x64e39af0f110: card 103 port 1 profiles inconsistent (1 < 3)
juin 19 10:37:36 hal pipewire-pulse[1561]: mod.protocol-pulse: 0x64e39af0f110: card 103 port 2 profiles inconsistent (1 < 3)
juin 19 10:38:19 hal bluetoothd[712]: profiles/audio/avdtp.c:cancel_request() Open: Connection timed out (110)
juin 19 10:38:19 hal pipewire[1179]: pw.node: (bluez_output.00_42_79_F0_F0_A6.1-117) running -> error (Received error event)
juin 19 10:38:21 hal bluetoothd[712]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:42:79:F0:F0:A6: Device or resource busy
juin 19 10:38:21 hal bluetoothd[712]: profiles/audio/avdtp.c:cancel_request() Abort: Connection timed out (110)
juin 19 10:38:23 hal pipewire[1179]: pw.node: (bluez_input_internal.00_42_79_F0_F0_A6.0-107) suspended -> error (Received error event)
juin 19 10:38:23 hal pipewire[1179]: pw.node: (bluez_output.00_42_79_F0_F0_A6.1-86) running -> error (Received error event)
juin 19 10:38:30 hal pipewire[1179]: pw.node: (bluez_input_internal.00_42_79_F0_F0_A6.0-107) suspended -> error (Received error event)
juin 19 10:38:30 hal pipewire[1179]: pw.node: (bluez_output.00_42_79_F0_F0_A6.1-86) running -> error (Received error event)
juin 19 10:38:32 hal bluetoothd[712]: src/device.c:search_cb() 00:42:79:F0:F0:A6: error updating services: Connection timed out (110)
juin 19 10:38:32 hal bluetoothd[712]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
juin 19 10:39:15 hal bluetoothd[712]: profiles/audio/avdtp.c:cancel_request() Open: Connection timed out (110)
juin 19 10:39:27 hal bluetoothd[712]: src/device.c:search_cb() 00:42:79:F0:F0:A6: error updating services: Connection timed out (110)
juin 19 10:39:27 hal bluetoothd[712]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
juin 19 10:39:41 hal bluetoothd[712]: profiles/audio/avdtp.c:cancel_request() Open: Connection timed out (110)
juin 19 10:39:55 hal bluetoothd[712]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
juin 19 10:41:42 hal bluetoothd[712]: profiles/audio/transport.c:set_volume() Unable to set volume: Transport endpoint is not connected (-107)I don't really know what you would need as outputs, so feel free to ask anything else. It's been a few months on Arch for me and I'm still learning !
Thank you in advance for your help
Last edited by cmtk89 (2024-06-19 11:39:17)
Offline
Looks related to this discussion & commit:
- https://lore.kernel.org/linux-bluetooth … gmail.com/
- https://git.kernel.org/pub/scm/linux/ke … efe77b6903
For some reason the fix has not been included in the stable trees, I will ask upstream why that is the case ![]()
Edit: Seems like the fix is already queued for stable: https://git.kernel.org/pub/scm/linux/ke … nect.patch
Last edited by gromit (2024-06-19 11:12:52)
Offline
OK great, so I guess I'll just have to wait.
I had been looking if there was any report on the issue but didn't really know where to find it.
I just had a look at the two links you posted, I understand roughly what it means but is there any more "readable" kind of "forum" to see the current issues with the kernel and report them maybe ?
Just a final question, how do I close the subject ? I just add [SOLVED] in the title ?
Thank you !
Offline
I had been looking if there was any report on the issue but didn't really know where to find it.
I just had a look at the two links you posted, I understand roughly what it means but is there any more "readable" kind of "forum" to see the current issues with the kernel and report them maybe ?
The kernel has a bugzilla, but its sometimes a bit unclear how this is actually used as apparently a lot of developers do not pay attention to it. Most workflows in the kernel community are somewhat email based, so this means no fancy UI's ![]()
For issues with the kernels provided in the Arch Linux repositories you can always check our bugtracker (here exemplary for the "linux" package, linux-zen, linux-lts etc have their own repositories) over at https://gitlab.archlinux.org/archlinux/ … x/-/issues and open an issue there if you cant find an already existing bug report.
There also is the kernel regression tracking overview, but that does not include everything: https://linux-regtracking.leemhuis.info/regzbot/stable/
Just a final question, how do I close the subject ? I just add [SOLVED] in the title ?
Thank you !
Yes I think so, not a pro with the forum rules myself ![]()
Offline
Seems like the fix is already queued for stable: https://git.kernel.org/pub/scm/linux/ke … nect.patch
If you want you can also test the stable release candidate that should include this patch:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-6.9.6rc1-1-x86_64.pkg.tar.zstOffline
If you want you can also test the stable release candidate
Thank you, I'll try if I find the time. If I'm not mistaken, the fix should be out in 6.9.6, the next version right ?
Offline
I have the same error, my earbuds connects, I start viewing a video and after some seconds disconnects. I looked at journalctl, bluetooth service but I can't figure out what's wrong.
Offline
same problem here:
ago 11 00:17:11 juan-nb wireplumber[1200]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_00_BB_43_D8_42_B7/sep1/fd2
ago 11 00:17:11 juan-nb plasmashell[1507]: org.kde.pulseaudio: No object for name "bluez_input.00:BB:43:D8:42:B7"
ago 11 00:17:11 juan-nb kded6[1407]: org.kde.pulseaudio: No object for name "bluez_input.00:BB:43:D8:42:B7"
ago 11 00:17:11 juan-nb pipewire[1198]: pw.node: (bluez_output.00_BB_43_D8_42_B7.1-86) running -> error (Received error event)
ago 11 00:17:11 juan-nb kded6[1407]: org.kde.pulseaudio: No object for name "bluez_output.00_BB_43_D8_42_B7.1"
ago 11 00:17:11 juan-nb plasmashell[1507]: org.kde.pulseaudio: No object for name "bluez_output.00_BB_43_D8_42_B7.1"
ago 11 00:17:11 juan-nb plasmashell[1507]: org.kde.pulseaudio: No object for name "bluez_input.00:BB:43:D8:42:B7"
ago 11 00:17:27 juan-nb systemd[822]: Started Konsole - Terminal.
ago 11 00:17:27 juan-nb konsole[2807]: QLayout: Cannot add a null widget to QHBoxLayout/
ago 11 00:17:27 juan-nb systemd[822]: Started app-org.kde.konsole-2807.scope.Offline
This thread and the fix is a year old, you don't have the same problem, but maybe similar symptoms, in which case opening up a new thread with exact information on your setup will be much more fruitful.
Closing this old thread.
Offline
Pages: 1
Topic closed