This is a collection of tips and information regarding blueman, a GTK+ bluetooth manager.
Be sure to enable the bluetooth daemon and start blueman with blueman-applet.
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
As long as you have gvfs-obexftp installed, you can use thunar from blueman to browse files remotely. Open up the blueman services configuration window and replace
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 gvfs-rar from AUR: https://aur.archlinux.org/packages.php?ID=23861
obex-data-server package is broken for now and needs to rebuild with:
$ ./configure --prefix=/usr --sysconfdir=/etc
Just grab it from ABS and rebuild.
>>For me now with actual obex-data-server and standard gvfs all is working fine (Yes obex-browsing too) the only thing is delete files on remote storage do not work.
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>
Can't 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).
https://bbs.archlinux.org/viewtopic.php?id=65889 - Discussion threads on problems