- 1 Installation
- 2 Usage
- 3 Blueman and PulseAudio
- 4 Troubleshooting
Blueman can be installed from the AUR.AUR package in the
Be sure to enable the Bluetooth daemon and start Blueman with
Be sure the local Bluetooth device is availabe by running
hcitool dev. If only
Devices: is dumped, the local Bluetooth device is unavailable. If this is the case, try restarting the bluetooth service or toggle the WiFi/Bluetooth switch on your laptop (if it exists). For example: the switch is
Fn+F3 on an Acer Aspire laptop. Also try rebooting to activate the local Bluetooth device. If you run
blueman-applet without an available local Bluetooth device, the Blueman tray icon will not appear.
blueman-applet, and the Blueman tray icon will show up. The following autostart file should have been created:
/etc/xdg/autostart/blueman.desktop meaning that Blueman should autostart with most desktop environments without intervention. See the wiki article for your desktop environment or window manager as well as the Autostarting article for further information on autostarting.
It might be necessary for the user to be added to the
lp group in order for the user to be able to add and manage Bluetooth devices using Blueman. See
/etc/dbus-1/system.d/bluetooth.conf for the section that enables users of the
lp group to communicate with the Bluetooth daemon.
To receive files remember to right click on the Blueman tray icon > Local Services > Transfer > File Receiving" and tick the square box next to "Enabled".
Mounting bluetooth devices without Nautilus
Blueman is configured to use Nautilus for bluetooth device mounting by default. The instructions below describe a method for using different file managers with Blueman. Thunar is used in this example. Substitute thunar with the name of your file manager if you are using something different.
#!/bin/bash fusermount -u ~/bluetooth obexfs -b $1 ~/bluetooth thunar ~/bluetooth
Now you will need to move the script to an appropriate location (e.g.,
/usr/local/bin). After that, mark it as executable:
# chmod +x /usr/local/bin/obex_thunar.sh
The last step is to change the line in Blueman tray icon > Local Services > Transfer > Advanced to
Blueman and PulseAudio
Users who want to use PulseAudio with a Bluetooth headset may want to activate the PulseAudio plugin of Blueman. This automatically loads PulseAudio Bluetooth module after audio device is connected and plays all audio through the Bluetooth headset.
Blueman and Thunar
nautilus --browse obex://
Workaround for a Bug with obex and gvfs
To browse mobile phone via nautilus with Blueman you need a patched GVFS. Install AUR. It is possible that you will need to rebuild the AUR package as shown below:AUR from
$ ./configure --prefix=/usr --sysconfdir=/etc
Workaround a bug with network manager in Bluetooth networking
Some distributions show all Bluetooth interfaces as net.80203, which can cause strange behaviour in network manager, for example NM trying to get dhcp address for an incoming connection.
Put this in
<?xml version="1.0" encoding="UTF-8"?> <deviceinfo version="0.2"> <device> <match key="info.category" string="net.80203"> <match key="net.interface" contains="bnep"> <merge key="info.category" type="string">net.bluetooth</merge> <merge key="info.product" type="string">Bluetooth Interface</merge> <merge key="info.capabilities" type="strlist">net, net.bluetooth</merge> <merge key="net.bluetooth.mac_address" type="copy_property">net.80203.mac_address</merge> <remove key="net.80203.mac_address"/> </match> </match> </device> </deviceinfo>
Cannot receive files
You have to edit
/etc/conf.d/bluetooth file and uncomment this line:
Blueman applet does not start
If blueman-applet fails to start, try removing the entire
/var/lib/bluetooth directory and restarting the machine (or just the dbus and bluetooth services).
# rm -rf /var/lib/bluetooth # reboot
If you see a notification saying
Incoming file over Bluetooth then this means that the device isn't marked as trusted. Mark it as trusted and try again (looking at the code, it looks like some buttons should be displayed in the notification, but I don't see them).