Comment 2 for bug 1859592

I read from previous bugs and forums on the internet that people seem to think this is BIOS _update_ related. Things don't just break from one day to the next because you suddenly need a firmware update. I tried a couple of things like going to BIOS and loading default settings. Save. Reboot. No change.

What finally DID resolve the problem was removing the power cable for a couple of seconds and putting it back in.

So although this issue can be closed, I have this deja vu that this kind of weird bluetooth issue happens once or twice per year, but only with Linux. Either this is a coincidence, or there is some kind of state, signal, message, or bit that Windows does or does not send, as opposed to Linux.