From ArchWiki
Revision as of 20:28, 5 January 2015 by Orschiro (talk | contribs) (Provided link to Github repo)
Jump to navigation Jump to search

Blueman is a full featured Bluetooth manager written in GTK+. Blueman versions 1.23 and below were developed on and used the, now unmaintained, Bluez4 bluetooth stack. In November 2013, Blueman development moved to Github. As of version 1.99.alpha1, Blueman has partial support for the Bluez5 bluetooth stack.


Note: Blueman is currently undergoing rapid development - not all functionality may work as expected.

Install either bluemanAUR or blueman-gitAUR (the development version) from the AUR.

Be sure to enable the Bluetooth daemon and start Blueman with blueman-applet. A graphical settings panel can be launched with blueman-manager.



The following autostart file should have been created: /etc/xdg/autostart/blueman.desktop. This means that Blueman should be autostarted with most desktop environments without manual intervention. See the article for your desktop environment or window manager as well as the Autostarting article for further information on autostarting.


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".

Note: If you are running Blueman in a session that is started with the startx command, you should add source /etc/X11/xinit/xinitrc.d/* to your ~/.xinitrc to make GNOME Files capable of browsing your devices.

Mounting Bluetooth devices without GNOME Files

Blueman is configured to use GNOME Files for bluetooth device mounting by default. The instructions below describe a method for using different file managers with Blueman. The examples in this section focus on Thunar. If you are using a different file manager, substitute thunar with the name of the file manager you are using.
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/

The last step is to change the line in Blueman tray icon > Local Services > Transfer > Advanced to %d.

Tip: If you do not want to create a script, you could just replace this command: nautilus --browse obex:// with this one: thunar obex:// in Local Services > Transfer > Advanced

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.


Cannot receive files

If you cannot receive files with Blueman, edit the /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
$ systemctl 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 sending the file again.

No adapters detected

If your Bluetooth applet or manager doesn't show or detect any Bluetooth adapter, you might be missing rfkill. Restart might be required.

No module named cairo

You are probably missing python. Restart required.

See also