Created attachment 1472965 [details] dmesg output Description of problem: There are no any bluetooth adapter found in the lynx7 tablet. This tablet has the Realtek RTL8723BS wifi/bluetooth chip. The wifi works normally. Version-Release number of selected component (if applicable): New 4.18.0 and earlier How reproducible: Always Steps to Reproduce: 1. Install the Fedora 27 or 28 to the tablet. 2. Check the bluetooth with bt-adapter -l or bluetoothctl. See near the clock. Actual results: bt-adapter -l or bluetoothctl does not found any bluetooth adapter. There is no bluetooth icon near the clock. Expected results: bt-adapter -l and bluetoothctl should find any bluetooth adapter. There should be the bluetooth icon near the clock. Additional info: Fedora automatically loads the r8723bs kernel module but does not load any bluetooth related modules. lsmod | grep -E 'bluetooth|bt' shows nothing. The problem and what I tried to do was described detailed here: https://forums.fedoraforum.org/showthread.php?318910-Driver-for-realtek-RTL8723BS-wifi-bluetooth-chip
Created attachment 1472978 [details] lsmod output
$ bt-adapter -l ** ERROR:lib/helpers.c:319:intf_supported: assertion failed: (introspection_proxy != NULL) Aborted (core dumped) $ dmesg -l err [ 8.327710] systemd-gpt-auto-generator[455]: Failed to dissect: Input/output error [ 8.329133] systemd[445]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1. $ journalctl --no-pager -b -p err -- Logs begin at Fri 2018-07-20 23:38:41 EEST, end at Fri 2018-08-03 15:50:12 EEST. -- Aug 03 14:31:13 lynx7 systemd-gpt-auto-generator[455]: Failed to dissect: Input/output error Aug 03 14:31:13 lynx7 systemd[445]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1. Aug 03 14:31:28 lynx7 wpa_supplicant[727]: bgscan simple: Failed to enable signal strength monitoring Aug 03 15:50:08 lynx7 systemd-coredump[1553]: Process 1546 (bt-adapter) of user 1000 dumped core. Stack trace of thread 1546: #0 0x00007fd4f3c41feb raise (libc.so.6) #1 0x00007fd4f3c2c5c1 abort (libc.so.6) #2 0x00007fd4f45db0f3 g_assertion_message.cold.16 (libglib-2.0.so.0) #3 0x00007fd4f463415e g_assertion_message_expr (libglib-2.0.so.0) #4 0x0000557aaed2cb19 intf_supported (bt-adapter) #5 0x0000557aaed2a6d8 main (bt-adapter) #6 0x00007fd4f3c2e24b __libc_start_main (libc.so.6) #7 0x0000557aaed2b17a _start (bt-adapter) Stack trace of thread 1548: #0 0x00007fd4f3cfa659 __poll (libc.so.6) #1 0x00007fd4f429c671 g_socket_condition_check (libgio-2.0.so.0) #2 0x00007fd4f42ef4c3 _g_socket_read_with_control_messages (libgio-2.0.so.0) #3 0x00007fd4f42ef5d0 _g_dbus_worker_do_read_unlocked (libgio-2.0.so.0) #4 0x00007fd4f42f17bf _g_dbus_worker_do_read_cb (libgio-2.0.so.0) #5 0x00007fd4f42abd54 g_task_return_now (libgio-2.0.so.0) #6 0x00007fd4f42abd8d complete_in_idle_cb (libgio-2.0.so.0) #7 0x00007fd4f46091cb g_idle_dispatch (libglib-2.0.so.0) #8 0x00007fd4f460c8ad g_main_context_dispatch (libglib-2.0.so.0) #9 0x00007fd4f460cc78 g_main_context_iterate.isra.21 (libglib-2.0.so.0) #10 0x00007fd4f460cfa2 g_main_loop_run (libglib-2.0.so.0) #11 0x00007fd4f42ef6ba gdbus_shared_thread_func (libgio-2.0.so.0) #12 0x00007fd4f4634f2a g_thread_proxy (libglib-2.0.so.0) #13 0x00007fd4f3782594 start_thread (libpthread.so.0) #14 0x00007fd4f3d050df __clone (libc.so.6) Stack trace of thread 1547: #0 0x00007fd4f3cfa659 __poll (libc.so.6) #1 0x00007fd4f460cbe6 g_main_context_iterate.isra.21 (libglib-2.0.so.0) #2 0x00007fd4f460cd10 g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fd4f460cd61 glib_worker_main (libglib-2.0.so.0) #4 0x00007fd4f4634f2a g_thread_proxy (libglib-2.0.so.0) #5 0x00007fd4f3782594 start_thread (libpthread.so.0) #6 0x00007fd4f3d050df __clone (libc.so.6) Aug 03 15:50:12 lynx7 abrt-notification[1606]: Process 1545 (bt-adapter) crashed in g_assertion_message_expr.cold.17()
Hi, the RTL8723BS doesn't have Bluetooth support in the 4.18 kernel. Upstream actually accepted a patch set that adds support for it (with ACPI) today[0] so support in Fedora should be coming soon(ish). [0] https://marc.info/?l=linux-bluetooth&m=153329827425571&w=2
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Hi. This bug still exists with the 4.18.10 kernel. There is no bluetooth adapter in the system. There is no bluetooth icon near the clock. The dmesg is attached. Some check: $ uname -r 4.18.10-200.fc28.x86_64 $ bt-adapter -l ** ERROR:lib/helpers.c:319:intf_supported: assertion failed: (introspection_proxy != NULL) Aborted (core dumped)
Created attachment 1489678 [details] kernel 4.18.10 dmesg
The wifi works normally as before.
The great wonder was happened. After the last fedora update the bluetooth adapter begun to work. All my bluetooth headsets work fine except new Philips SHB3075. This adapter can not find the Philips headset. The bt-adapter -d command can not find this headset too. BTW the same problem is with new cheap chinese bluetooth USB adapter CSR 4.0. The Meizu M5s smartphone can not find this headset too. It is strange but very old bluetooth USB adapter in notebook can find this headset. A big thanks to all developers who had done a great work!!!
Check in the lynx7 tablet: $ bt-adapter -l Available adapters: lynx7 (08:D8:34:89:2A:D8) $ bt-adapter -i [hci0] Name: lynx7 Address: 08:D8:34:89:2A:D8 Alias: lynx7 [rw] Class: 0xc0104 Discoverable: 1 [rw] DiscoverableTimeout: 0 [rw] Discovering: 0 Pairable: 1 [rw] PairableTimeout: 0 [rw] Powered: 1 [rw] UUIDs: [HeadsetAudioGateway, 00001801-0000-1000-8000-00805f9b34fb, AVRemoteControl, 00001800-0000-1000-8000-00805f9b34fb, PnPInformation, AVRemoteControlTarget, AudioSource, AudioSink, Headset] $ bt-device -l Added devices: P47 (DD:A4:9A:C9:5A:6B) SVEN AP-B450MV (E9:08:EF:50:06:13) EDIFIER W800BT (04:FE:A1:EC:B4:3C) --------------------- Check in the notebook with old bluetooth USB adapter which can find Philips SHB3075 headset: $ bt-adapter -l Available adapters: dell (00:15:83:3D:0A:57) $ bt-adapter -i [hci0] Name: dell Address: 00:15:83:3D:0A:57 Alias: dell [rw] Class: 0x2c010c Discoverable: 1 [rw] DiscoverableTimeout: 0 [rw] Discovering: 0 Pairable: 1 [rw] PairableTimeout: 0 [rw] Powered: 1 [rw] UUIDs: [HeadsetAudioGateway, AudioSource, AudioSink, AVRemoteControl, PnPInformation, AVRemoteControlTarget, Handsfree] $ bt-device -l Added devices: Philips SHB3075 (A4:77:58:73:50:C6) RX-TX-10 (A6:53:19:34:4C:A7) SVEN AP-B450MV (E9:08:EF:50:06:13) $ bt-device -i A4:77:58:73:50:C6 [A4:77:58:73:50:C6] Name: Philips SHB3075 Alias: Philips SHB3075 [rw] Address: A4:77:58:73:50:C6 Icon: audio-card Class: 0x240404 Paired: 1 Trusted: 1 [rw] Blocked: 0 [rw] Connected: 1 UUIDs: [SerialPort, Headset, AudioSink, AVRemoteControlTarget, AdvancedAudioDistribution, AVRemoteControl, Handsfree]
Hi, Right I forgot to add a comment to this bug. The kernel work I've been doing for the RTL8723BS support has landed in 4.19 and I recently also pushed the necessary firmware files to linux-firmware. So indeed bluetooth should work now :) As for your single headset not working, it seems that that just is a really strange headset. Since it does not work with multiple different bluetooth receivers, this seems to be unrelated to this bug. You could try sending a mail about this to: linux-bluetooth.org, maybe someone can help you debug the headset issue further there. Regards, Hans
Hi! A wonder again. :) I had discovered the secret of this sly Philips headset. I held the second button, then heard the short sound signal and the headset was appeared in bluetooth manager of tablet. The same thing with smartphone. Seem like the headset by default is invisible for "alien" devices So everything is fine. No bugs. You can close this issue. Best regard, Sergiy.