[arch-general] bluetooth pairing with cellphone
hey dudes. I fail (sort of) at pairing my pc with my phone via bluetooth. (sony ericsson k810i, pc uses broadcom dongle) I have a system where everything is up to date, bluez is installed etc. the configs are all pretty much default. I did need to enable HID2HCI_ENABLE="true" in /etc/conf.d/bluetooth otherwise the bluetoothd daemon would abort immediately after startup ( ? ) I can do `hcitool scan` and see my phone. But to pair... 1) the bluez-simple-agent way: I start `sudo bluez-simple-agent`,it listens, and on the phone I search new devices. phone cannot find pc :( 2) the blueman way: 2a ) If I run as regular user, I get: dieter@dieter-ws-a7n8x-arch ~ blueman-manager Loading configuration plugins _________ on_bluez_name_owner_changed (/usr/bin/blueman-manager:99) org.bluez owner changed to :1.6 Using gconf config backend _________ SetAdapter (/usr/lib/python2.6/site-packages/blueman/gui/DeviceList.py:293) None ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.33" (uid=1000 pid=5982 comm="/usr/bin/python /usr/bin/blueman-manager ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=4642 comm="/usr/sbin/bluetoothd ")) Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 578, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/usr/bin/blueman-manager", line 148, in on_bluez_name_owner_changed self.List = ManagerDeviceList(adapter=self.Config.props.last_adapter, inst=self) File "/usr/lib/python2.6/site-packages/blueman/gui/manager/ManagerDeviceList.py", line 71, in __init__ DeviceList.__init__(self, adapter, data) File "/usr/lib/python2.6/site-packages/blueman/gui/DeviceList.py", line 120, in __init__ self.SetAdapter(adapter) File "/usr/lib/python2.6/site-packages/blueman/gui/DeviceList.py", line 324, in SetAdapter except dbus.DBusServiceUnknownError: AttributeError: 'module' object has no attribute 'DBusServiceUnknownError' do i need to be in some kind of group or something? There was no post install message, nor info about this on the wiki page (http://wiki.archlinux.org/index.php/Bluetooth) 2b) if I run blueman-manager as root I can pair (hooray). But actually I don't want to run stuff as root, nor do I want to use the bloatware that is blueman-manager. Dieter
hello dieter, try phonetooth from AUR. works great with my 610i. --
On Mon, 24 Aug 2009 19:19:57 +0200 vlad <vla@uni-bonn.de> wrote:
hello dieter,
try phonetooth from AUR. works great with my 610i.
Thanks for the idea. But i'm trying to avoid any additional apps. I mean, it _should_ work with bluez-simple-agent. and obexfs kicks the ass of any tool such as phonetooth :) (it mounts your phone as a fuse filesystem) Dieter
hi, On Mon, Aug 24, 2009 at 07:23:58PM +0200, Dieter Plaetinck wrote:
Thanks for the idea. But i'm trying to avoid any additional apps. I mean, it _should_ work with bluez-simple-agent. and obexfs kicks the ass of any tool such as phonetooth :) (it mounts your phone as a fuse filesystem)
sorry, i cannot give you any constructive advice. but none of the common applications worked for me. so i ended up using phonetooth. bluetooth is one of the hackiest things under linux. when i used kde3 kdebluetooth did a very good job. with kde4 it doesn't work at all (though i haven't tried it for months). vlad --
Dieter Plaetinck schrieb:
I have a system where everything is up to date, bluez is installed etc. the configs are all pretty much default. I did need to enable HID2HCI_ENABLE="true" in /etc/conf.d/bluetooth otherwise the bluetoothd daemon would abort immediately after startup ( ? )
Your bluetooth dongle shows in the system as a HID device. This allows operating systems that are not bluetooth-aware (or even the bootloader) to use a bluetooth keyboard or mouse. hid2hci switches your bluetooth dongle to HCI mode, so you have full bluetooth functionality. I've never had such a dongle before.
ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.33" (uid=1000 pid=5982 comm="/usr/bin/python /usr/bin/blueman-manager ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=4642 comm="/usr/sbin/bluetoothd "))
This error is different from the one we had on the weekend. Probably because none of us thought about "ps ax|grep bluetoothd"
do i need to be in some kind of group or something? There was no post install message, nor info about this on the wiki page (http://wiki.archlinux.org/index.php/Bluetooth)
I still think this is some dbus permission stuff, but that is voodoo for me.
2b) if I run blueman-manager as root I can pair (hooray).
But actually I don't want to run stuff as root, nor do I want to use the bloatware that is blueman-manager.
You only need to pair once, so you don't need root for now. However, it would be nice to do the next pairing without it.
I haven't tested this out yet, but I don't see why it shouldn't work. Edit /etc/system.d/bluetooth.conf by adding the following lines before <policy at_console="true">: [code] <policy group="btuser"> <allow send_destination="org.bluez"/> <allow send_interface="org.bluez.Agent"/> </policy> [/code] Then create the group btuser and add yourself to it. Restart dbus or your computer. You should probably then be able to pair as yourself. As a note, I don't know if you need the send_interface as well, but I assume you do. MAQ. On Mon, Aug 24, 2009 at 2:08 PM, Thomas Bächler <thomas@archlinux.org>wrote:
Dieter Plaetinck schrieb:
I have a system where everything is up to date, bluez is installed etc. the configs are all pretty much default. I did need to enable HID2HCI_ENABLE="true" in /etc/conf.d/bluetooth otherwise the bluetoothd daemon would abort immediately after startup ( ? )
Your bluetooth dongle shows in the system as a HID device. This allows operating systems that are not bluetooth-aware (or even the bootloader) to use a bluetooth keyboard or mouse. hid2hci switches your bluetooth dongle to HCI mode, so you have full bluetooth functionality.
I've never had such a dongle before.
ERROR:dbus.proxies:Introspect error on org.bluez:/:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.33" (uid=1000 pid=5982 comm="/usr/bin/python /usr/bin/blueman-manager ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=4642 comm="/usr/sbin/bluetoothd "))
This error is different from the one we had on the weekend. Probably because none of us thought about "ps ax|grep bluetoothd"
do i need to be in some kind of group or something? There was no post
install message, nor info about this on the wiki page ( http://wiki.archlinux.org/index.php/Bluetooth)
I still think this is some dbus permission stuff, but that is voodoo for me.
2b) if I run blueman-manager as root I can pair (hooray).
But actually I don't want to run stuff as root, nor do I want to use the bloatware that is blueman-manager.
You only need to pair once, so you don't need root for now. However, it would be nice to do the next pairing without it.
participants (4)
-
Dieter Plaetinck
-
Qadri
-
Thomas Bächler
-
vlad