OK, sudo dmesg | grep -i bluetooth
has yielded a result:
[ 13.651786] Bluetooth: Core ver 2.22
[ 13.651806] NET: Registered PF_BLUETOOTH protocol family
[ 13.651807] Bluetooth: HCI device and connection manager initialized
[ 13.651812] Bluetooth: HCI socket layer initialized
[ 13.651814] Bluetooth: L2CAP socket layer initialized
[ 13.651819] Bluetooth: SCO socket layer initialized
[ 13.993541] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.993545] Bluetooth: BNEP filters: protocol multicast
[ 13.993550] Bluetooth: BNEP socket layer initialized
[ 15.980086] Bluetooth: hci0: command 0xfc05 tx timeout
[ 15.980093] Bluetooth: hci0: Reading Intel version command failed (-110)
And that error leads me to another post on this very forum from a user with broken Bluetooth begging for help:
I am with you: I would avoid Bluetooth if I had another option, but I need a wireless headset that also works with my phone, and Bluetooth is the only game in town that covers that niche. I only just started using it myself to allow me to talk and move around my office, and had been pleasantly surprised how well it worked… right up until it didn’t. I wish there was a “Bluetooth Pro” that worked over WiFi so at least there was an alternative to Bluetooth.
Intel Bluetooth and WiFi keep breaking on Manjaro, it seems. I have now found a litany of posts going back years that would seem to explain the terrible experience some of my friends and family have been having with Bluetooth and Intel AX200 Wireless on Manjaro (as I said, I am fairly new to Bluetooth and Manjaro, so this is the first time I have been impacted). When I search for the explicit error Reading Intel version command failed (-110)
in the last month the only distros that seem to be impacted are Manjaro and Ubuntu.
I am not sure if the flakiness originates within Manjaro or upstream in Arch. While it also seems to impact Ubuntu, RedHat/Fedora don’t seem to have the same flakiness. Perhaps I need to have a deeper look at nobara.