This commit is contained in:
Harald Hope 2021-04-16 21:12:52 -07:00
parent 991a35d665
commit 573c272bda

View file

@ -362,11 +362,14 @@ that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have: Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped * * Bluetooth Service: enabled/disabled
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop * * Bluetooth Service: started/stopped
rfkill: software: block/unblock; hardware: block/unblock - however, for * bluetoothctl: start/stop
hardware, that means a physical button has been pressed to disable it, on the * bt-adapter: start/stop
laptop that is. * hciconfig: start/stop
* rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it, changed something, for example, if I rfkill blocked hci0, then unblocked it,