Am Sonntag 31 Dezember 2006 15:40 schrieb Marcel Holtmann: > > Beside that, running the dbus command suggested in this bug report works, > > too. It should be noted, though, that you have to be root. > > No. You have to be console user (or root).
I cite from dbus policy that I somehow just don't get (too many english words are different between dbus-send manpage, policy snippet and dbus-api.txt :-O The policy for bluez-utils: <policy user="root"> <allow own="org.bluez"/> </policy> <policy at_console="true"> <allow send_destination="org.bluez.Adapter"/> <allow receive_sender="org.bluez.Adapter"/> <allow send_path="/org/bluez/Adapter"/> <allow send_destination="org.bluez.Manager"/> <allow receive_sender="org.bluez.Manager"/> <allow send_path="/org/bluez/Manager"/> <allow send_destination="org.bluez.Security"/> <allow receive_sender="org.bluez.Security"/> </policy> As you can see, they differ between root and console users. And somehow, the part for the console users does not match this command: dbus-send --system --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable To show what I mean (dbus-send matches the above line): $ cd /var/lib/bluetooth/<BDADDR-of-hci0> $ cat config mode discoverable $ dbus-send .......:off $ cat config mode off $ dbus-send .......:connectable $ cat config mode off $ dbus-send .......:discoverable $ cat config mode off Maybe one of you know why only setting to "off" works but not the other two mode settings? All three commands work as user root. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]