![]() So, in short, NetworkManager is unable to activate the Bluetooth interface. Only then a subsequent systemctl restart bluetooth command seems to make it work again and change to "on" state as well as start listing nearby devices. ![]() So it seems the NetworkManager is unable to activate it back. However, if I switched it back off and on using NetworkManager applet, it is again not working and Bluetooth stays in "off" state. It immediately works and connects to devices correctly. Indeed, it is "soft blocked" : # rfkill list ![]() Logs indicate a problem with rfkill : 22:22:46 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)Ģ2:22:46 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)Ģ2:19:44 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)Ģ2:13:44 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)Ģ2:13:43 bluetoothd: Failed to set mode: Blocked through rfkill (0x12) By default, after a fresh boot, the Bluetooth service is unable to start correctly and does not find any device to pair with nor the NetworkManager's Bluetooth indicator changes from "off" to "on" state.īus 002 Device 002: ID 8087:0029 Intel Corp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |