Arch Linux

Bisection results:

c80f3668982a3bc53d1655eeb48f5640181ae65f is the first bad commit
commit c80f3668982a3bc53d1655eeb48f5640181ae65f
Author: andyrtr <andyrtr@eb2447ed-0c53-47e4-bac8-5bc4a241df78>
Date: Tue Feb 28 17:06:57 2017 +0000

db-move: moved bluez from [testing] to [extra] (i686, x86_64)

git-svn-id: file:///srv/repos/svn-packages/svn@289676 eb2447ed-0c53-47e4-bac8-5bc4a241df78

:040000 040000 9a4aaddae103f6bb5b11ce1c43f9a62aa298ea90 12beda89c505d7cb6c870fceb05445c825fd4e34 M repos

Bisection should be done with upstream code, not with packages.

http://www.bluez.org/contact/

At my notebook (Lenovo X220) I observer similar crashes.

Some of my debugging work, when running bluetoothd in gdb:

Breakpoint 1, browse_cb (recs=0x717f60, err=0, user_data=0x725790) at src/device.c:4523
4523 struct btd_adapter *adapter = device->adapter;
(gdb) p device->adapter
Cannot access memory at address 0x10157
(gdb)

As seen the device->adapter pointer is not valid, not sure why.

I diffed the upstream source between versions, and it seems like they slightly redid A2DP

Please bring it to the linux-bluetooth@vger.kernel.org ML.

I can absolutely confirm this.
Bluetooth module: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Bluetooth device: Jabra Halo Smart 1.8.1
Journalctl says: kernel: bluetoothd[530]: segfault at 10 ip 000000000046b634 sp 00007ffcd39f2160 error 4 in bluetoothd (deleted)[400000+da000]
More stacktraces:
ystemd-coredump[6623]: Process 530 (bluetoothd) of user 0 dumped core.

Stack trace of thread 530:
#0 0x000000000046b634 ba2str (bluetoothd)
#1 0x0000000000469673 n/a (bluetoothd)
#2 0x0000000000469d82 n/a (bluetoothd)
#3 0x00000000004472d3 n/a (bluetoothd)
#4 0x000000000047a31d n/a (bluetoothd)
#5 0x0000000000447405 n/a (bluetoothd)
#6 0x00007f30cc10745a g_main_context_dispatch (libglib-2.0.so.0)
#7 0x00007f30cc107810 n/a (libglib-2.0.so.0)
#8 0x00007f30cc107b32 g_main_loop_run (libglib-2.0.so.0)
#9 0x000000000040b6b2 n/a (bluetoothd)
#10 0x00007f30cb6dd511 __libc_start_main (libc.so.6)
#11 0x000000000040bf0a n/a (bluetoothd)

Steps to reproduce:
- Delete bluetooth headset from blueman (or gnome-bluetooth)
- Search using Blueman, attempt to connect to A2DP.
- Blueman appears to reach a connection, however shortly after the connection bars appear, Blueman crashes and complains about no present bluetooth adapter. This is likely the point where the crash listed above happens
- On restart of Bluetooth the Headset still appears paired, however only the low-quality headset profile is available. Once connected it is able to channel audio for some time, but will lead to continuous connection losses and reconnects.

I wonder if this issue is connected? https://bugs.archlinux.org/task/53424

Also see this Ubuntu thread: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1616695

From the Ubuntu ticket:
"So what I did was downgrade my Bluez & Bluez-libs from 5.44 to 5.41-2 and all is good in the bluetooth world!"
Also: Cysioland has reported the bug to the ML and filed a bug for it
- https://www.spinics.net/lists/linux-bluetooth/msg70136.html
- https://bugzilla.kernel.org/show_bug.cgi?id=195221

Just as an idea, it's worth to test the fix regarding gdm user that's spawning pulseaudio: https://wiki.archlinux.org/index.php/Bluetooth_headset#Gnome_with_GDM

I reverted to 5.41-2 and had to do that quick-fix for it to work, documented everything: https://ubuntulinuxx.wordpress.com/2017/06/13/connecting-skullcandy-hesh-2-wireless-headphones-to-bluetooth-on-archlinux/

NOTE: I know that reverting to a previous version is not the best way to fix the issue...

@dminca I needed that fix under 5.41-2 to make things work, and it still doesn't help with newest version.

And I can understand your post being profanity laced, but please, HFP/HSP and A2DP carry audio, not video, please correct that, for fox sake.

I am aware of the Audio protocols used. Have you tried switching profile to A2DP via `pacmd set-card-profile [id] a2dp_sink`?

New update out. Has this been fixed?

Just ran the latest update from Manjaro, and the audio quality is working great!,watching a video is not so good, the audio sync off just by passing my hand between headphones and laptop. BLUEZ 5.46.1 installed today.

I ran into the same issue and downgraded from 5.46-1 to 5.41-2 where my headphones work out of the box. Before downgrading I tried loading pulseaudio's bt modules after starting X11 and not at boot as per[1] which was not working - so I reverted back to how the configs were before.

[1] https://gist.github.com/freyes/dfc3f5232526a62bbc09adc816e0477d

https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=5252296b725ef159992be5372f60721bd9adca48

Check if this is the fix for your issues. It will be included in the next release.

WHen is the next release supposed to be out?

I build and installed the aur package bluez-git.

I am able to pair with my bose soundbar ( https://www.bose.com/en_us/products/speakers/home_theater/bose-solo-5-tv-sound-system.html#v=solo_5_black ). The bluetooth daemon does not immediately connect to the soundbar after pairing (which it did with ver 5.43-2). The dameon does not crash anymore.

I can connect to the soundbar only after turning the soundbar off and on again - but the sound is still played through my internal soundcard.

I am still downgrading to bluez 5.43-2 which was the last working version for me.

Issue no longer occurring on latest BlueZ v5.47-2.

I was now able to connect the Wireless Headset to A2DP without encountering any errors, it just works all of a sudden.

@Cysioland - is it fixed for you too?

It pairs, but there are major synchronization issues, as @JoaoHerberto mentioned

Is this still an issue?

Yes, it is still an issue with the most recent bluez-git version 5.48

Now I get a segfault, when trying to connect to my bose solo soundbar. I did the following:

$ bluetoothctl
[NEW] Controller 00:09:DD:60:XX:XX ChromeLinux_5E0F [default]
[NEW] Device 08:DF:1F:82:XX:XX Bose Solo 5 system
Agent registered
[bluetooth]# pair 08:DF:1F:82:XX:XX
Attempting to pair with 08:DF:1F:82:XX:XX
[CHG] Device 08:DF:1F:82:XX:XX Connected: yes
[CHG] Device 08:DF:1F:82:XX:XX Paired: yes
Pairing successful
[CHG] Device 08:DF:1F:82:XX:XX Connected: no
[bluetooth]# connect 08:DF:1F:82:XX:XX
Attempting to connect to 08:DF:1F:82:XX:XX
[CHG] Device 08:DF:1F:82:C8:9E Connected: yes
[CHG] Device 08:DF:1F:82:C8:9E UUIDs: 00001000-d102-11e1-9b23-XXXXXXXXXXXX
[CHG] Device 08:DF:1F:82:C8:9E UUIDs: 0000110b-0000-1000-8000-XXXXXXXXXXXX
[CHG] Device 08:DF:1F:82:C8:9E UUIDs: 0000110c-0000-1000-8000-XXXXXXXXXXXX
[CHG] Device 08:DF:1F:82:C8:9E UUIDs: 0000110e-0000-1000-8000-XXXXXXXXXXXX
[CHG] Device 08:DF:1F:82:C8:9E UUIDs: 00001800-0000-1000-8000-XXXXXXXXXXXX
[CHG] Device 08:DF:1F:82:C8:9E UUIDs: 00001801-0000-1000-8000-XXXXXXXXXXXX
[CHG] Device 08:DF:1F:82:C8:9E ServicesResolved: yes
Connection successful


Edit: At this point I opened Gnome bluetooth settings which immediately leads to crashing the bluetooth daemon:
[CHG] Controller 00:09:DD:60:EA:56 Discovering: yes
Agent unregistered
[DEL] Controller 00:09:DD:60:EA:56 ChromeLinux_5E0F [default]
Waiting to connect to bluetoothd...


dmesg is showing:

[ 105.005346] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 105.028514] bluetoothd[441]: segfault at 8 ip 000055d1ddd408e0 sp 00007ffcfab35da8 error 4 in bluetoothd[55d1ddcdf000+f4000]


Edit #2: If I connect to the bose soundbar by only using the console pairing, connection and sound seems to work ... Until I open the gnome bluetooth settings. So this might be another issue dealing with the combination gnome <> bluez.

I'm also observing core dumps in bluetooth.service using bluez 5.49 trying to connect to an A2DP sink.
5.48-[12] and 5.47-[34] work as expected.

[13282.131766] bluetoothd[27969]: segfault at 8 ip 0000560754342fd0 sp 00007ffef4000b68 error 4 in bluetoothd[5607542df000+f8000]

Not sure if this is still the same bug. At least please report this to the bluez mailing list or upstream tracker.

hi!

not sure if this is the same bug, so i opened a new task: https://bugs.archlinux.org/task/58094

here is the commit that might fix this: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e10c204e1226e94a1eaaeaee076e7e2e5b13c504

Please try 5.49-2 in testing.

still getting the same error. https://pastebin.com/Eg3hMYun

ps: i might be wrong, but it could be that the patch you applied worked when built against the current master, not 5.49. if i understood sjanc correctly, this is the patch we should cherrypick: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=2c3bba7b38be03834162e34069156f1fd49f0528

Please heck 5.49-3 with that commit included.

If this is still not enough please try on top of 5.49 locally before requesting to add somewhat random commits. Every cherry picking can have unwanted side affects.

5.49-3 works, thank you. also, i did not request random commits, but 2 commits that actually fix this bug. i did describe the difference between the two in my post, which was closed (i specifically pointed out the first patch was applied to the current master, not 5.49).

thank you for packaging this up, it works now.

Has the initial issue for other users also been solved?

I will be able to retest it on sunday evening.

5.49-3 solved for me, thank you!

5.49-3 solved it for me, too.

I am able again
- to pair with my bose speakers
- to connect to them
- to open gnome bluetooth settings without crashing anything