My bluetooth stuff no longer works, and when I run bluetooth-applet I get: Agent registration failed: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Adapter" member "RegisterAgent" error name "(unset)" destination "org.bluez") /etc/dbus-1/system.d/bluetooth.conf looks ok, so I don't know why it is blocking access.
*** This bug has been marked as a duplicate of bug 475068 ***
Alright, not a duplicate. My bad.
Maybe related to bug 475096 (https://bugzilla.redhat.com/show_bug.cgi?id=475096) "Bluetooth USB dongle not detected under Gnome". At least looking at bug number... :-) 69->96
Which version of dbus?
The /etc/dbus-1/system.d/bluetooth.conf file needs: <allow send_destination="org.bluez"/>
Incidentally it should also *not* have: <allow send_path="/"/> <allow send_path="/org/bluez"/> The first rule allows anyone to send a message to the object "/" which is bad. The destination rules should be enough.
(In reply to comment #4) > Which version of dbus? dbus-1.2.6-1.fc10.i386 bluetooth.conf has: <allow send_path="/"/> <allow send_path="/org/bluez"/> No time to test manual modification right now I'm afraid.
This is what BlueZ should be using and it is exactly what I committed upstream: <policy user="root"> <allow own="org.bluez"/> <allow send_destination="org.bluez"/> </policy> <policy at_console="true"> <allow send_destination="org.bluez"/> </policy> <policy context="default"> <deny send_destination="org.bluez"/> </policy> New packages for F10 should follow shortly.
does not seem to work with with test-discovery patch below tested with F10, bluez-4.22, bluetooth mouse diff -ru a/src/bluetooth.conf b/src/bluetooth.conf --- a/src/bluetooth.conf 2008-12-05 14:08:45.000000000 -0500 +++ b/src/bluetooth.conf 2008-12-08 18:17:07.000000000 -0500 @@ -12,7 +12,7 @@ </policy> <policy at_console="true"> - <allow send_path="/"/> + <allow send_path="*"/> <allow send_destination="org.bluez.Manager"/> <allow receive_sender="org.bluez.Manager"/> @@ -28,6 +28,8 @@ </policy> <policy context="default"> + <allow send_requested_reply="true" send_type="signal"/> + <deny send_destination="org.bluez.Manager"/> <deny receive_sender="org.bluez.Manager"/>
If these is about the missing DeviceFound signals, then that is a total different discussion. The signals should be allowed always and there is a D-Bus patch that fixes this.
what about the agent Dec 8 19:51:48 kcrashtop bluetoothd[2243]: Agent replied with an error: org.freedesktop.DBus.Error.AccessDenied, A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Agent" member "RequestPinCode" error name "(unset)" destination ":1.56")
Does it help if you add a <allow send_interface="org.bluez.Agent"/> to at_console section?
it did work in the default section
My bad. It actually has to go into the user="root" section since bluetoothd is sending the message to an agent running as normal user. Can you please double-check that moving it into the user="root" section makes it work.
It works. On a side note, everything is suddenly able to pair using bluetooth applet I was not able to cleanly pair my a2dp or keyboard til now
*** Bug 475436 has been marked as a duplicate of this bug. ***
*** Bug 475096 has been marked as a duplicate of this bug. ***
*** Bug 475279 has been marked as a duplicate of this bug. ***
*** Bug 475459 has been marked as a duplicate of this bug. ***
How exactly /etc/dbus-1/system.d/bluetooth.conf file should look like? Mine is now: <policy user="root"> <allow own="org.bluez"/> <allow send_destination="org.bluez"/> <allow send_interface="org.bluez.Agent"/> </policy> <policy at_console="true"> <allow send_destination="org.bluez"/> </policy> <policy context="default"> <deny send_destination="org.bluez"/> </policy> And I can see my Bluetooth settings (Visibility, Friendly Name, Known Devices) and I can send files to my phone from Nautilus via 'Send To...' plugin. However, BT icon is not present (unless I check 'Always display icon' opposed to 'Only display when adaptor is present'), I can't setup a new device as it can't find any BT devices, also 'Send files to device...' and 'Browse files on device...' options after right-click on icon are greyed out.
bluez-utils-3.35-5.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/bluez-utils-3.35-5.fc8
bluez-utils-3.36-3.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/bluez-utils-3.36-3.fc9
We still have an issue with the signals. That has to be decided by D-Bus upstream first on how we continue. Either they add a global allow for signals or we have to do it for every daemon.
bluez-4.22-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/bluez-4.22-2.fc10
bluez-4.22-2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bluez'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2008-11087
bluez-utils-3.35-5.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing-newkey update bluez-utils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-11103
bluez-utils-3.36-3.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing-newkey update bluez-utils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-11119
Hi, I'm still having problems after update it (F10). I can't pairing any device, and it don't find any device. I can't send any file to the phone that is already paired (before the bug), in the transfer windows can see "org.openobex.Error.ConnectionAttempFaild" All the best, Miguel
*** Bug 475989 has been marked as a duplicate of this bug. ***
*** Bug 476116 has been marked as a duplicate of this bug. ***
I have the same problem above. When I try to send a file to my Nokia phone, it says "org.openobex.Error.ConnectionAttempFaild". When I try to browse the device, it says "DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)". I'm testing on F10, using bluez 4.22-2. Follows dmesg output: usb 4-2: new full speed USB device using uhci_hcd and address 4 usb 4-2: configuration #1 chosen from 1 choice usb 4-2: New USB device found, idVendor=1caa, idProduct=0001 usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 I need very much to use bluetooth (specially file transfer), but I can't use it on my desktop (F10) only on my laptop (Ubuntu Hardy). If you need any more information, say me and I'll do what I can to help. Best regards.
bluez-utils-3.36-3.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
bluez-4.22-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
bluez-utils-3.35-5.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
I am having trouble getting my BT dongle working. Its a Belkin F8T009 and has worked before and works fine with other distro's. Is it a bluez4 problem? The relevant part of /var/log/messages reads... bluetoothd: HCI dev 0 up bluetoothd: Starting security manager 0 bluetoothd: Registered interface org.bluez.Service on path /org/bluez/1923/hci0 bluetoothd: Can't write to class od device: Unknown error 4294967186 (-110) kernel: hci_cmd_task: hci0 command tx timeout I can't find reference to this error anywhere, but I'd be surprised if I was the only one getting it.
(In reply to comment #33) > bluez-4.22-2.fc10 has been pushed to the Fedora 10 stable repository. If > problems still persist, please make note of it in this bug report. This update did not fix bluetooth for me either.
(In reply to comment #36) > (In reply to comment #33) > > bluez-4.22-2.fc10 has been pushed to the Fedora 10 stable repository. If > > problems still persist, please make note of it in this bug report. > > This update did not fix bluetooth for me either. That's very unlikely given that the dbus changes were reverted later on... File a new bug if it's actually broken.