Booting up an Ubuntu computer or attempting to toggle Bluetooth in GNOME Settings only to find the wireless interface missing and system logs reporting Failed to start Bluetooth Service (or entering a terminal and discovering bluetooth.service: Failed with result 'exit-code') disables wireless audio and peripheral connections. The bluetoothd daemon is a fundamental system service provided by the BlueZ Linux Bluetooth stack responsible for managing HCI (Host Controller Interface) hardware adapters, broadcasting discovery beacons, and negotiating pairing keys. When this service crashes or fails to initialize, desktop Bluetooth controls disappear and commands like bluetoothctl hang. This failure typically stems from software RF kill blocks, missing proprietary firmware binaries for Intel or Realtek Bluetooth chipsets, or corrupted BlueZ configuration files. Unblocking radio hardware and reinstalling BlueZ packages restores wireless connectivity.
Unblock Hardware and Software Radio Blocks Using rfkill
Linux features a kernel-level radio frequency kill switch (rfkill) subsystem that disables Bluetooth power when hardware hotkeys or airplane mode are triggered.
- Open a terminal shell and query the status of all wireless radio transceivers:
rfkill list - Examine the entry for Bluetooth. If either Soft blocked or Hard blocked displays as
yes, kernel power to the adapter is suspended. - Unblock all radio interfaces by executing:
sudo rfkill unblock bluetooth - Verify that the state switches to
Soft blocked: no. - If hard-blocked, check physical laptop toggle switches or function key combinations (e.g. Fn + F2) on your chassis.
Inspect Error Diagnostics and Reload the btusb Kernel Module
The Linux USB Bluetooth bus driver (btusb) can enter a hung state if the computer resumed from sleep or experienced an electrical bus reset.
- Query recent systemd error logs for the Bluetooth service:
journalctl -xeu bluetooth.service - Look for kernel firmware loading errors such as Bluetooth: hci0: Failed to load firmware file.
- Unload and reload the primary Bluetooth kernel driver module to reset the physical controller:
sudo modprobe -r btusb && sudo modprobe btusb - Check kernel dmesg logs to confirm that the hardware controller initializes:
sudo dmesg | grep -i blue
Reinstall the BlueZ Package and Restart the Bluetooth Daemon
Corrupted configuration plists in /etc/bluetooth/main.conf cause the bluetoothd daemon to abort execution upon startup.
- Reinstall the BlueZ daemon and proprietary hardware firmware packages:
sudo apt update && sudo apt install --reinstall bluez linux-firmware - Reload the systemd daemon manager configuration:
sudo systemctl daemon-reload - Enable and restart the Bluetooth service:
sudo systemctl enable --now bluetooth && sudo systemctl restart bluetooth - Verify that the daemon reports active (running):
systemctl status bluetooth - Launch the interactive control utility to confirm device pairing:
bluetoothctl show