[SOLVED] Bluetooth dies when i connect a device (slackware64 current)

Nille_kungen · 07-01-2021, 02:29 PM

Every time when i start my bluetooth headset/headphones and it connects bluetooth dies right after i hear the confirmation of connection in my headset.
I then need to run 'sudo /etc/rc.d/rc.bluetooth start' and then choose to connect headphones by clicking the bluetooth icon in systray and chose to connect.
I think it stopped working correctly after the bluez upgrade in June for current (i don't upgrade current all the time).
I'm don't have any knowledge with bluetooth or if i need to clean any config for it to work without crashing.

marav · 07-01-2021, 02:38 PM

Quote:

Originally Posted by Nille_kungen

Every time when i start my bluetooth headset/headphones and it connects bluetooth dies right after i hear the confirmation of connection in my headset.
I then need to run 'sudo /etc/rc.d/rc.bluetooth start' and then choose to connect headphones by clicking the bluetooth icon in systray and chose to connect.
I think it stopped working correctly after the bluez upgrade in June for current (i don't upgrade current all the time).
I'm don't have any knowledge with bluetooth or if i need to clean any config for it to work without crashing.

Do you use pipewire or pulseaudio ?

FYI, Bluetooth + pipewire works perfectly with all my BT devices.

Nille_kungen · 07-01-2021, 03:08 PM

Quote:

Originally Posted by marav

Do you use pipewire or pulseaudio ?

FYI, Bluetooth + pipewire works perfectly with all my BT devices.

I haven't set up any pipewire so i guess PA, i don't know what needs to be done to setup pipewire.
It used to work perfectly for me as well but not any more.

alex14641 · 07-01-2021, 05:55 PM

Is there anything relevant in logs when bluetoothd dies?

Nille_kungen · 07-02-2021, 10:03 AM

Quote:

Originally Posted by alex14641

Is there anything relevant in logs when bluetoothd dies?

Not that means anything to me.

Code:

syslog
Jul  2 16:48:21 darkstar bluetoothd[1164]: profiles/audio/avdtp.c:caps_to_list() Invalid capability data in getcap resp
Jul  2 16:48:22 darkstar acpid: input device has been disconnected, fd 17

Code:

messages
Jul  2 16:48:20 darkstar kernel: input: SBKP 4 A1 (AVRCP) as /devices/virtual/input/input14
Jul  2 16:48:21 darkstar elogind-daemon[1161]: Watching system buttons on /dev/input/event13 (SBKP 4 A1 (AVRCP))

Code:

dmesg
[ 2763.050461] input: SBKP 4 A1 (AVRCP) as /devices/virtual/input/input14

Nille_kungen · 07-02-2021, 10:30 AM

There seems to be problems with A2DP in bluez 5.59, i just tried git and it works again.

marco70 · 07-02-2021, 01:06 PM

Fix problem patch for gentoo:

https://gitweb.gentoo.org/repo/gento...ss/bluez/files

https://gitweb.gentoo.org/repo/gento...-parsing.patch

bluez 5.59

chrisVV · 07-03-2021, 04:33 AM

The gentoo repo is down at the moment. For anyone who wants the patch, an alternative repo is on github, which seems to be working OK: https://github.com/gentoo/gentoo/blo...-parsing.patch and in the bluez git repo at https://git.kernel.org/pub/scm/bluet...8de0a12b4364d4

Nille_kungen · 07-03-2021, 01:34 PM

I also had to remove and re-pair the device for it to work as expected.
Instead of patching one can also compile bluez current or revert to 5.58
I compiled both bluez current and 5.58 and both works.

The patch was first posted in this bug report.
https://github.com/bluez/bluez/issues/157