Difference between revisions of "Blueman"

From ArchWiki
Jump to: navigation, search
(Workaround for a Bug with obex and gvfs)
(Discussion Threads on problems: clarified by changing section name)
Line 37: Line 37:
== Please help to figure the probs out ==
== Discussion Threads on problems ==

Revision as of 04:27, 11 April 2009

This is a collection of tips and information regarding blueman, a GTK+ bluetooth manager. The information here was originally collated from the AUR thread at http://aur.archlinux.org/packages.php?ID=13870.


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: http://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.

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.

This is for versions <= 1.01, versions 1.02 and up will include this patch.

Put this in /etc/hal/fdi/information/bnep.fdi:

<?xml version="1.0" encoding="UTF-8"?>

<deviceinfo version="0.2">
   <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"/>

Discussion Threads on problems