Troubleshooting
The least information we typically need to help with an issue is the version of blueman you're using. In most cases the BlueZ version makes sense as well. You can use the following template to make sure you're providing the most basic information:
blueman:
BlueZ:
Distribution:
Desktop environment:
It may also be useful to provide the debugging output from the next section, sometimes even multiple examples (e.g. a working one and one where the issue comes up). Please use some service like Pastebin or GitHub Gists to post your logs and keep the thread clean and readable. Make sure to describe the exact steps you took when producing it.
To retrieve useful information, the best starting point is to run blueman-applet from a Terminal window. It needs to be shut down, since only one instance may be running. You should always be able to do that with killall blueman-applet.
There will be plenty of output in the Terminal window, also including messages from blueman-manager. If you're unsure how to get behind a given problem, please provide the full output in your error report.
The blueman-report tool is a simple helper to log blueman output. It also provides a way to comment on the steps you take while creating the log and uploads the commented log file.
To test if your device is recognized by BlueZ you can use tools that list all Bluetooth devices on your machine. The following command are supposed to be run from a terminal.
- For BlueZ version 4 run:
bluez-test-adapter list - For Bluez version 5 run
bluetoothctl list
Example output, BlueZ 5
# bluetoothctl list
[NEW] Controller 00:02:72:C5:BB:B4 infirit [default]
[NEW] Device 6C:83:36:B9:C6:D6 Galaxy Nexus
BlueZ 4
# bluez-test-adapter list
[ /org/bluez/740/hci0 ]
Name = vbox-xubuntu-0
Powered = 1
Devices = dbus.Array([dbus.ObjectPath('/org/bluez/740/hci0/dev_6C_83_36_B9_C6_D6'), dbus.ObjectPath('/org/bluez/740/hci0/dev_7C_2F_80_3B_AF_AB'), dbus.ObjectPath('/org/bluez/740/hci0/dev_14_99_E2_02_67_9A')], signature=dbus.Signature('o'), variant_level=1)
DiscoverableTimeout = 0
PairableTimeout = 0
Discoverable = 1
Address = 00:02:72:C5:BB:B4
Discovering = 0
Pairable = 1
Class = 0x000000
UUIDs = dbus.Array([dbus.String(u'00001000-0000-1000-8000-00805f9b34fb'), dbus.String(u'00001001-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000112d-0000-1000-8000-00805f9b34fb'), dbus.String(u'00001112-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000111f-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000111e-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000110c-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000110e-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000110a-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000110b-0000-1000-8000-00805f9b34fb')], signature=dbus.Signature('s'), variant_level=1)
If there are no controllers listed you either have,
- A hardware killswitch enabled, usually called "airplane mode".
- The adapter is not supported by the Linux bluetooth stack.
To check the later, you can find the hardware ID with lsusb or lspci depending on the interface to google for it.
If you require turning on your bluetooth device at boot time automatically, for instance when you require keyboard / mouse support. You can add a udev rule to enable that. Additionally, you need to make sure you have the package bluez-utils installed.
Create a file in /etc/udev/rules.d/ (eg 50-bluetooth-hci-auto-poweron.rules) with the following content.
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/bin/hciconfig %k up"