Description of problem: To trigger the issue: * Connect to a remote bluetooth speaker (Marshall model) Version-Release number of selected component: bluez-5.46-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: browse_cb executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=fd12e7d7dd6640b38d897ac357bd83b6;i=2fe3;b=a1fd1a21dee14bbba99e76c461d293fc;m=39a4ae153;t=558d95ea9df49;x=79ed43e4fa9ac5ca kernel: 4.12.9-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 browse_cb at src/device.c:4574 #1 search_completed_cb at src/sdp-client.c:205 #2 sdp_process at lib/sdp.c:4354 #3 search_process_cb at src/sdp-client.c:230 Potential duplicate: bug 1459322
Created attachment 1328068 [details] File: backtrace
Created attachment 1328069 [details] File: cgroup
Created attachment 1328070 [details] File: core_backtrace
Created attachment 1328071 [details] File: cpuinfo
Created attachment 1328072 [details] File: dso_list
Created attachment 1328073 [details] File: environ
Created attachment 1328074 [details] File: exploitable
Created attachment 1328075 [details] File: limits
Created attachment 1328076 [details] File: maps
Created attachment 1328077 [details] File: open_fds
Created attachment 1328078 [details] File: proc_pid_status
Created attachment 1328079 [details] File: var_log_messages
Similar problem has been detected: When connecting a Soundlink Mini speaker via bluetooth to the Fedora system it is failing without any particular reason. When checking "dmsg", the following line is logged: [ 134.779803] bluetoothd[1341]: segfault at 10 ip 000055aa98c78474 sp 00007ffd1ff95d60 error 4 in bluetoothd[55aa98bfc000+e7000] This issue seems to be reproducable on multiple different bluetooth audio devices, while other bluetooth devices seems to be working fine. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: browse_cb executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=9fa2257b53654124b540c36b533afcdf;i=9cc4;b=ee24e94a1fb64303bc5b34e86f4f5cb4;m=3899ab6e87;t=559b546c15b0d;x=45c1c99c2e4371ba kernel: 4.12.13-300.fc26.x86_64 package: bluez-5.46-6.fc26 reason: bluetoothd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1469961 has been marked as a duplicate of this bug. ***
Closed an older report of the issue as it seems to be a dupe of this issue. The issue was meanwhile reported to the bluez mailing list on 21.08.2017 in subject "Segfault on audio pairing". No further results regarding it there however so far.
*** Bug 1495310 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Toda a vez que conecto a caixa de som bluetooth JBL Charger 3 ocorre este erro. Com outros dispositivos conecta normalmente, testei conectando a um iPhone 6S iOS 11.0.1 e conecta normalmente, o bug é apenas com a caixa de som JBL Charger 3. Every time I connect to JBL Charger 3 bluetooth sound box this error has occurred. I tested connecting to iPhone 6S iOS 11.0.1 and connected OK, normaly, the bug is only with a JBL Charger 3 sound box. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: browse_cb executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=56acaaf2d8ec418da2c2afc6ddcb9d54;i=f76c;b=165650022a2246199d3bc08075932dc3;m=235e2d3f;t=55a8f9c43a529;x=da529029d14fe44e kernel: 4.12.14-300.fc26.x86_64 package: bluez-5.46-6.fc26 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: Toda vez que conecta a JBL Charger3 o Bluetooh trava e não responde. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: browse_cb executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=56acaaf2d8ec418da2c2afc6ddcb9d54;i=187c3;b=ba5d1b2f08d34461b7dd532834715e46;m=11302809;t=55bd0f7a6537b;x=511297dd2e44dc28 kernel: 4.13.5-200.fc26.x86_64 package: bluez-5.46-6.fc26 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
The issue is not reproducable for me anymore after upgrading to Fedora 27.
Similar problem has been detected: bluetoothd fail with SIGSEGV when connecting to my Jabra STORM v1.16.0 headset. There is no problem with other bluetooth devices like my Beats headphones. $ bluetoothctl [bluetooth]# connect A5:01:A5:10:96:32 Attempting to connect to A5:01:A5:10:96:32 [CHG] Device A5:01:A5:10:96:32 Paired: yes Failed to connect: org.bluez.Error.InProgress [CHG] Device A5:01:A5:10:96:32 Connected: yes ## SIGSEGV happens here ## Agent unregistered [DEL] Controller 00:02:72:B0:BD:52 dhLinux [default] reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: browse_cb executable: /usr/libexec/bluetooth/bluetoothd journald_cursor: s=b5cf9f13ab7c4074b60db972b6a6b87e;i=1524589;b=a4c79eb57145460f813a5669762ec43f;m=283ce996025;t=560f39e624d44;x=ec24a0ce088e2950 kernel: 4.13.13-200.fc26.x86_64 package: bluez-5.46-6.fc26 reason: bluetoothd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
(In reply to Florian Sievert from comment #19) > The issue is not reproducable for me anymore after upgrading to Fedora 27. I can confirm, connection is working with my Jabra STORM v1.16.0 headset after F27 upgrade. I suppose the key is the BlueZ stack upgrade from 5.46 (f26) to 5.47 (f27).
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.