Difference between revisions of "Blueman"

From ArchWiki
Jump to: navigation, search
(wikify some external links, use https for archlinux.org)
(Disable auto power-on)
 
(87 intermediate revisions by 16 users not shown)
Line 1: Line 1:
 
[[Category:Bluetooth]]
 
[[Category:Bluetooth]]
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 https://aur.archlinux.org/packages.php?ID=13870.
+
[[ja:Blueman]]
 +
{{Related articles start}}
 +
{{Related|Bluetooth}}
 +
{{Related|Bluez4}}
 +
{{Related articles end}}
 +
[https://github.com/blueman-project/blueman Blueman] is a full featured Bluetooth manager written in [[GTK+]]. Blueman versions 1.23 and below were developed on [https://launchpad.net launchpad.net] and used the, now unmaintained, [[Bluez4]] bluetooth stack. In November 2013, Blueman development moved to [https://github.com/blueman-project/blueman Github]. As of version 2.0, Blueman has full support for the Bluez5 Bluetooth stack.
  
==Installation==
+
== Installation ==
  
# pacman -S blueman
+
Install either {{Pkg|blueman}} or {{AUR|blueman-git}} (the development version).
  
Be sure to add the bluetooth daemon to rc.conf and start blueman with blueman-applet.
+
Be sure to enable the [[Bluetooth]] daemon and start Blueman with {{ic|blueman-applet}}. A graphical settings panel can be launched with {{ic|blueman-manager}}.
  
==Blueman and pulseaudio==
+
== Usage ==
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.
+
  
 +
=== Autostarting ===
  
== Troubleshooting ==
+
The following autostart file should have been created: {{ic|/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.
=== 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://
+
with
+
  thunar obex://
+
  
=== NOW obsolete! >> Workaround for a Bug with obex and gvfs ===
+
=== Permissions ===
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:
+
To receive files remember to right click on the ''Blueman tray icon > Local Services > Transfer > File Receiving (Object Push)'' and tick the ''Accept files from trusted devices'' box.
$ ./configure --prefix=/usr --sysconfdir=/etc
+
Just grab it from [[ABS]] and rebuild.
+
  
 +
To be able to manage devices, you might need to add your user to the {{ic|lp}} group, else you might receive the following error when connecting to a device: {{ic|DBusFailedError: No such file or directory}}. This is because the user needs to be authorized to communicate with the bluetooth daemon via [[D-Bus]] - the {{ic|lp}} group is specified in {{ic|/etc/dbus-1/system.d/bluetooth.conf}}. For information on adding a user to a group, see [[Users and groups#Other examples of user management]].
  
>>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.
+
=== Mounting Bluetooth devices ===
  
=== Workaround a bug with network manager in bluetooth networking ===
+
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.
  
Some distributions show all bluetooth interfaces as net.80203, which can cause strange behaviour in network manager,
+
{{hc|obex_thunar.sh|
for example NM trying to get dhcp address for an incoming connection.
+
#!/bin/bash
 +
fusermount -u ~/bluetooth
 +
obexfs -b $1 ~/bluetooth
 +
thunar ~/bluetooth
 +
}}
  
This is for versions <= 1.01, versions 1.02 and up will include this patch.
+
Now you will need to move the script to an appropriate location (e.g., {{ic|/usr/local/bin}}). After that, mark it as executable:
 +
# chmod +x /usr/local/bin/obex_thunar.sh
  
Put this in <code>/etc/hal/fdi/information/bnep.fdi</code>:
+
The last step is to change the line in ''Blueman tray icon > Local Services > Transfer > Advanced'' to {{ic|obex_thunar.sh %d}}.
  
<pre>
+
{{Out of date|It would appear that {{ic|thunar obex://%d}} is not functional. Also note that changing command should not be necessary as the system default file manager will be used by default - see release notes for 1.99.alpha2|Talk:Blueman#thunar obex:// support}}
<?xml version="1.0" encoding="UTF-8"?>
+
  
<deviceinfo version="0.2">
+
{{Tip|If you do not want to create a script, you could just replace this command: {{ic|nautilus --browse obex://}} with this one: {{ic|thunar obex://}} in ''Local Services > Transfer > Advanced''}}
<device>
+
 
  <match key="info.category" string="net.80203">
+
=== Blueman and PulseAudio ===
    <match key="net.interface" contains="bnep">
+
 
        <merge key="info.category" type="string">net.bluetooth</merge>
+
Users who want to use [[PulseAudio]] with a Bluetooth headset, in addition to [[install]]ing {{Pkg|pulseaudio-bluetooth}}, 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. For more information see [[Bluetooth headset]]
        <merge key="info.product" type="string">Bluetooth Interface</merge>
+
 
        <merge key="info.capabilities" type="strlist">net, net.bluetooth</merge>
+
== Configuration ==
        <merge key="net.bluetooth.mac_address" type="copy_property">net.80203.mac_address</merge>
+
Configuration is done through {{Pkg|dconf}} (or gsettings or {{Pkg|dconf-editor}}).
        <remove key="net.80203.mac_address"/>
+
 
    </match>
+
=== Disable auto power-on ===
  </match>
+
 
  </device>
+
Blueman automatically enables Bluetooth adapter ({{ic||rfkill unblock bluetooth}}) when certain events (on boot, laptop lid is opened, ...) occur. This can be disabled with the {{ic|auto-power-on}} in {{ic|org.blueman.plugins.powermanager}}:
</deviceinfo>
+
 
</pre>
+
$ gsettings set org.blueman.plugins.powermanager auto-power-on false
 +
 
 +
== Troubleshooting ==
 +
 
 +
=== Blueman applet does not start ===
 +
 
 +
If blueman-applet fails to start, try removing the entire {{ic|/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 {{ic|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 ===
 +
 
 +
{{Accuracy|Is {{Pkg|rfkill}} genuinely required? It's not a {{Pkg|blueman}} dependency and my bluetooth adaptor is detected just fine by blueman without it.}}
 +
 
 +
If your Bluetooth applet or manager doesn't show or detect any Bluetooth adapter, you might be missing {{Pkg|rfkill}}. Restart might be required.
  
 
=== Can't receive files ===
 
=== Can't receive files ===
You have to edit /etc/conf.d/bluetooth file and uncomment this line:
 
<pre>
 
#SDPD_ENABLE="true"
 
</pre>
 
  
== Discussion Threads on problems ==
+
If you can't send or receive files and you encounter a python-dbus-exception error similar or exactly like {{ic|process org.bluez.obex exited with status 1}} then it is advised to start the obexd-service manually from {{ic|/usr/lib/bluetooth/obexd}} and see if that helps. Since the default permissions assume 755 it is possible to start the daemon from a user-account and/or create an autostarter.
https://bbs.archlinux.org/viewtopic.php?id=65889
+
 
 +
Should the error persist or another occur then try using {{Pkg|obexftp}} for file transfers instead, see [[Bluetooth#ObexFTP transfers]].
 +
 
 +
== See also ==
 +
 
 +
* [https://github.com/blueman-project/blueman Blueman development], on GitHub

Latest revision as of 23:58, 18 April 2016

Related articles

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

Installation

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

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

Usage

Autostarting

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.

Permissions

To receive files remember to right click on the Blueman tray icon > Local Services > Transfer > File Receiving (Object Push) and tick the Accept files from trusted devices box.

To be able to manage devices, you might need to add your user to the lp group, else you might receive the following error when connecting to a device: DBusFailedError: No such file or directory. This is because the user needs to be authorized to communicate with the bluetooth daemon via D-Bus - the lp group is specified in /etc/dbus-1/system.d/bluetooth.conf. For information on adding a user to a group, see Users and groups#Other examples of user management.

Mounting Bluetooth devices

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.

obex_thunar.sh
#!/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 obex_thunar.sh %d.

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: It would appear that thunar obex://%d is not functional. Also note that changing command should not be necessary as the system default file manager will be used by default - see release notes for 1.99.alpha2 (Discuss in Talk:Blueman#thunar obex:// support)
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, in addition to installing pulseaudio-bluetooth, 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. For more information see Bluetooth headset

Configuration

Configuration is done through dconf (or gsettings or dconf-editor).

Disable auto power-on

Blueman automatically enables Bluetooth adapter () when certain events (on boot, laptop lid is opened, ...) occur. This can be disabled with the auto-power-on in org.blueman.plugins.powermanager:

$ gsettings set org.blueman.plugins.powermanager auto-power-on false

Troubleshooting

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

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: Is rfkill genuinely required? It's not a blueman dependency and my bluetooth adaptor is detected just fine by blueman without it. (Discuss in Talk:Blueman#)

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

Can't receive files

If you can't send or receive files and you encounter a python-dbus-exception error similar or exactly like process org.bluez.obex exited with status 1 then it is advised to start the obexd-service manually from /usr/lib/bluetooth/obexd and see if that helps. Since the default permissions assume 755 it is possible to start the daemon from a user-account and/or create an autostarter.

Should the error persist or another occur then try using obexftp for file transfers instead, see Bluetooth#ObexFTP transfers.

See also