Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.
What to Do When Bluetooth Is Not Working on Ubuntu
Kevin Wu
August 27, 2026· Updated October 4, 2026· 9 min read
When Bluetooth is not working on Ubuntu, find the first stage that fails: the adapter is missing or blocked, the Bluetooth service has stopped, the accessory is not discoverable, pairing or connection fails, or only the audio profile is wrong. If the Bluetooth switch will not turn on, check the adapter and rfkill first, then the service.
Ubuntu's troubleshooting guidance covers adapter recognition, power, discoverability, and support limits, while its connection guide adds range and passkey confirmation.［1］［2］ An accessory that is already connected to another host may also need to be disconnected according to its manufacturer's instructions. Do not erase every pairing to diagnose one accessory.
Key Takeaways:
- Separate controller, radio, discovery, pairing, trust, connection, and audio-profile states.
- Preserve service logs and remove only one recoverable pairing when evidence shows it is stale.
- Do not delete the Bluetooth database, weaken pairing security, or install unverified firmware.
Why won't Bluetooth turn on in Ubuntu?
Match what you see to the stage that usually explains it, then start at that step:
| What you see | Likely cause | Start at |
|---|---|---|
| No Bluetooth panel or no controller listed | Adapter not detected, unsupported, or missing a driver | Step 1 |
| The switch flips back to off | Soft or hard rfkill block | Step 1 |
bluetoothctl keeps waiting to connect to bluetoothd | Bluetooth service stopped or failed | Step 2 |
| Bluetooth is on but detects no devices | Accessory not in pairing mode, out of range, or held by another host | Step 3 |
Step 1: If Bluetooth is not working on Ubuntu, confirm the controller first
Run read-only checks:
bluetoothctl list
bluetoothctl show
rfkill list bluetooth
bluetoothctl exposes controllers and their state, while rfkill reports software and hardware radio blocks.［3］［4］ If no controller appears, check whether the hardware is detected with lsusb or lspci -nnk, then inspect the Ubuntu release’s official hardware support.
A soft block can normally be cleared through system controls or rfkill unblock bluetooth. A hard block points to a physical switch, firmware, or platform state. Do not install random firmware or disable security controls to force a controller online. For software provenance, see Ubuntu package source choices and safe DEB installation.
If more than one controller is listed, record which one is the default and which bus each controller uses. A built-in controller and a USB adapter can fail independently. Do not power off or remove every controller just to make the list shorter; first determine which controller saw the accessory when the setup last worked.
Capture the controller address only in a private support record and redact it when it is not needed. The important fields are power, discoverable/pairable state, and supported capabilities. A controller that exists but cannot be powered belongs to a different branch from a controller that powers on but discovers nothing.
Step 2: Check the Ubuntu Bluetooth service
Read service state and recent messages:
systemctl status bluetooth --no-pager
journalctl -u bluetooth -b --no-pager
If the service is inactive or failed, preserve the error, then restart the Bluetooth service once with sudo systemctl restart bluetooth. Repeated failure belongs to package, hardware, firmware, or policy diagnosis. Do not delete /var/lib/bluetooth; it contains system pairing state and removing it is a broad, destructive reset.
Limit journal sharing to the relevant boot and time window. Logs can include device names, addresses, usernames, or other nearby hardware. Record the first error and any preceding controller event rather than posting the entire system journal.
After one restart, rerun bluetoothctl show and the exact failed operation. If the service stops again, do not create a restart loop. Preserve the new failure and move to package, kernel, hardware, or policy support with the before-and-after state.
Step 3: Prepare the other device for discovery
Charge the accessory, place it close to the computer, and put it in its documented pairing mode. Ubuntu recommends keeping the device within 5–10 meters, making it discoverable, and confirming the displayed passkey when prompted. If it is connected to a phone, tablet, or another computer, check the accessory manufacturer's instructions before disconnecting it.
Use the desktop Bluetooth panel first. For diagnostic control:
bluetoothctl
power on
scan on
devices
Stop scanning after the device appears. The bluetoothctl manual documents controller, scan, pair, trust, and connect operations. Do not publish a complete scan containing nearby device names and addresses.
Use only the accessory manufacturer's documented method to enter pairing mode. Many devices expose a short pairing window or reconnect automatically to their last host. If another host owns the active connection, disconnect it normally or turn off its Bluetooth temporarily when that is safe; do not reset every saved host unless the manufacturer's recovery procedure requires it.
If the accessory never appears, compare one other known-good Bluetooth device with the same Ubuntu controller. That distinguishes an accessory-specific discovery problem from a controller-wide one. Keep the test device nearby and charged, and stop repeated scans that do not add evidence.
Step 4: Pair, trust, and connect as separate states
Inside bluetoothctl, use the exact address shown for the intended device:
pair DEVICE-ADDRESS
connect DEVICE-ADDRESS
info DEVICE-ADDRESS
Watch prompts on both devices and compare passkeys before accepting. Do not lower pairing security or accept an unexpected prompt. Pairing stores identity and keys; connection establishes the active link. Use info DEVICE-ADDRESS to inspect whether the device is already Trusted. Run trust DEVICE-ADDRESS only for a device you own or control when you intentionally want BlueZ to treat it as trusted for future authorization; use untrust DEVICE-ADDRESS to reverse that choice. Success at one stage does not prove the next.
If one known accessory has a recoverable pairing procedure and its saved record is clearly stale, remove only that device and pair it again:
remove DEVICE-ADDRESS
Do not bulk-remove devices or clear the Bluetooth database. Confirm that the accessory can be put back into pairing mode before removing its record.
After pairing, test connect before adding trust. Some accessories work without persistent trust, and managed systems may restrict that choice. When trust is appropriate for a device you control, document why it is needed and verify that untrust restores the prior authorization behavior.
If pairing fails, copy the exact error and note whether a passkey appeared on both sides. Do not repeatedly accept mismatched codes. A timeout before confirmation, an authentication rejection, and a successful pair followed by connection failure are separate results and should not be repaired with the same action.
Step 5: Separate connection from Bluetooth audio profile problems
If info says Connected but sound does not use the headset, the Bluetooth link may be healthy. Check Ubuntu Sound settings for the correct output/input device and an appropriate profile. High-quality playback and headset microphone modes can use different profiles and capabilities. A missing microphone profile is not the same as a failed pair.
Test one known audio file and one input meter. Do not repeatedly delete the pairing while changing sound profiles; that destroys the comparison. If only audio fails after a system update, record the Ubuntu version, audio server state, and device capabilities for support.
Also test the accessory's non-audio function when available. Media controls or battery reporting can confirm that the Bluetooth link is active even when audio routing is wrong. Conversely, seeing the device name in Sound settings does not prove the selected profile supports both high-quality playback and microphone input.
Change one sound setting at a time and return to the original profile if the test fails. Do not install a replacement audio stack or random codec package during a basic Bluetooth connection investigation; that changes ownership of an otherwise working link.
Step 6: Escalate with stage-specific evidence
Escalate hardware/controller absence to the computer or adapter vendor with Ubuntu version, kernel, IDs, and logs. Escalate an accessory that cannot enter pairing mode or connect to any host to its manufacturer. Managed systems may intentionally disable Bluetooth; contact the administrator rather than bypassing policy. If Wi-Fi, USB, or audio devices fail at the same time, the device and app troubleshooting guide helps separate a system-wide fault from an accessory one.
Name the last successful stage in the report: controller present, radio unblocked, service active, device discovered, paired, trusted if applicable, connected, or audio profile selected. Include only the command output needed to prove that boundary and redact unrelated nearby devices. This lets support start at the unresolved stage instead of asking you to erase all pairings.
Summary
Confirm the controller, rfkill, and service first. Prepare the other device, then distinguish discovery, pairing, trust, and connection. Remove only one recoverable pairing when evidence supports it. If the link is connected, move to the audio-profile branch instead of wiping Bluetooth state or installing random firmware.
FAQ
Why does Ubuntu show no Bluetooth controller?
Hardware may be disabled, undetected, unsupported, missing firmware, or blocked by platform policy. Check controller output and hardware IDs before installing anything.
What does a hard rfkill block mean?
It reflects a hardware or platform radio state and normally cannot be cleared by software alone.
Why is my accessory not discovered?
It may be out of range, not discoverable, discharged, or unsupported. It may also be connected to another host; check the accessory's instructions before disconnecting it.
Are paired, trusted, and connected the same?
No. Pairing stores keys, trust controls authorization behavior, and connection is the active link.
Should I delete /var/lib/bluetooth?
No. That broadly destroys system pairing state and is not a safe single-device troubleshooting step.
When is it safe to remove a paired device?
Only when you can identify the exact device, reproduce its pairing mode, and accept losing that one saved relationship.
Why is Bluetooth connected but audio is wrong?
The output device or audio profile may be wrong. Check sound settings instead of pairing again.
Should I install firmware from an online script?
No. Use Ubuntu repositories, documented hardware support, or the device manufacturer with a rollback path.
Disclaimer: Bluetooth capabilities depend on the controller, accessory, Ubuntu release, kernel, firmware, and audio stack. Preserve logs and pairing recovery before changes.
Sources:
- Ubuntu Desktop Guide — I cannot connect my Bluetooth device — https://help.ubuntu.com/stable/ubuntu-help/bluetooth-problem-connecting.html.en
- Ubuntu Desktop Guide — Connect your computer to a Bluetooth device — https://help.ubuntu.com/stable/ubuntu-help/bluetooth-connect-device.html.en
- Ubuntu Manpage Repository — bluetoothctl(1) — https://manpages.ubuntu.com/manpages/resolute/man1/bluetoothctl.1.html
- Ubuntu Manpage Repository — rfkill(8) — https://manpages.ubuntu.com/manpages/jammy/man8/rfkill.8.html
Sources checked 4 October 2026.
Related Articles:
