Comment 6 for bug 1980473

Hmm. No clue what went wrong. Found a solution via Dr. Google from Suse for here that I don't understand (why it worked, and what went wrong yesterday?):

# rfkill block bluetooth
# rfkill unblock bluetooth
# hciconfig hci0 down
# rmmod btusb
# modprobe btusb
# hciconfig hci0 up

Keeping my fingers crossed it remains @ working; and that it might help you as well!

For the nerds: here is what happened during these commands
[ 9438.293727] Bluetooth: hci0: command 0x0c03 tx timeout
[ 9446.293851] Bluetooth: hci0: sending initial HCI reset command failed (-110)
[ 9454.850055] usb 1-7: new full-speed USB device number 61 using xhci_hcd
[ 9454.999552] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01
[ 9454.999555] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 9455.016884] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 9455.017745] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 9455.297906] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[ 9455.315101] Bluetooth: hci0: Intel firmware patch completed and activated
[ 9455.376994] NET: Registered protocol family 38
[ 9455.399814] Bluetooth: RFCOMM TTY layer initialized
[ 9455.399821] Bluetooth: RFCOMM socket layer initialized
[ 9455.399825] Bluetooth: RFCOMM ver 1.11
[ 9476.985656] usbcore: deregistering interface driver btusb
[ 9488.659672] usbcore: registered new interface driver btusb
[ 9488.674893] Bluetooth: hci0: read Intel version: 370810011003110e32
[ 9488.674895] Bluetooth: hci0: Intel device is already patched. patch num: 32