Hi, I’m trying to resume a thread from the old Ubuntu One forum, here.
My Bluetooth used to connect, and then stopped.
Searching in Settings > Bluetooth (slider set to “On”) returns no devices, just a spinning wheel. The GUI blueman-manager returns nothing when I search. Back when the problem started, it retained information about paired devices, but would not connect. Unpairing has resulted in their permanent disappearance.
When I try to link it from another device, say my phone, it is detected, but attempt to pair fails even after verifying
There was no unusual event that preceded. My computer had been knocked off a desk some months before, which had (not immediately) led to the wireless ceasing to function, and it seems conceivable to me that the Bluetooth difficulties are also a delayed response, but I have always had difficulties setting up Bluetooth and want to rule out OS difficulties. Ubuntu 22.04 is the only OS running on this laptop. I have tried booting into recovery mode and a slightly older kernel without increased success.
I have been trying to follow the advice linked here.
I run sudo apt reinstall --purge bluez gnome-bluetooth-sendto without incident.
sudo systemctl disable tlp.service returns the response
tlp.service is not a native service, redirecting to systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install disable tlp
; this happens no matter how many times I run it, and also happens on rebooting, so I am not sure if it is actually doing what it is supposed to.
lsmod | grep bluetooth returns
bluetooth 1028096 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic 16384 2 bluetooth
The response to sudo systemctl status bluetooth includes “enabled” and “running.”
sudo rm -r /var/lib/bluetooth/ proceeds without incident.
sudo apt reinstall --purge bluez gnome-bluetooth-sendto again works fine.
hciconfig gives an address and no errors.
bluetoothctl gives “Agent registered” but no “[CHG] Controller” clause.
sudo rfkill unblock all runs without incident.
Back at the bluetoothctl prompt, power on and scan on are fine. The former gives the expected “Changing power on succeeded[.]” The latter finally returns a “[CHG] Controller” address and “Discovering: yes” ; however, nothing is actually discovered and I don’t know how to proceed.
sudo rfkill block bluetooth
sudo rfkill unblock bluetooth
doesn’t help.
Neither do discoverable on and discoverable on and agent NoInputNoOutput.
The computer is also not discovered on my phone.
A suggestion I’ve seen online suggests sudo apt remove blueman. No errors exist after this, but scan on no longer produces the “[CHG] Controller” address.
Is there anything left to try?