bluez-utils can't start in dbus mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Won't Fix
|
Medium
|
Charles Majola |
Bug Description
because of too strict security policies, hcid can't start if configured to use dbus:
root@lia /etc/init.d $hcid -n
hcid[6244]: Bluetooth HCI daemon
hcid[6244]: Can't get system message bus name: Connection ":1.117" is not allowed to own the service "org.bluez" due to security policies in the configuration file
hcid[6244]: Unable to get on D-BUS
(/etc/bluetooth
adding an appropriate policy to /etc/dbus-
<!DOCTYPE busconfig PUBLIC "-//freedesktop
"http://
<busconfig>
<!-- This configuration file specifies the required security policies
for BlueZ hcid to work. -->
<!-- ../system.conf have denied everything, so we just punch some holes -->
<policy user="root">
<allow own="org.bluez"/>
</policy>
<policy at_console="true">
<allow send_destinatio
<allow receive_
<allow send_path=
<allow send_destinatio
<allow receive_
<allow send_path=
</policy>
</busconfig>
root@lia /etc/init.d $hcid -n
hcid[6278]: Bluetooth HCI daemon
hcid[6278]: Starting security manager 0
Changed in bluez-utils: | |
assignee: | nobody → chmj |
ubuntu dapper,
dbus: 0.60-6ubuntu3
bluez-utils: 2.24-0ubuntu4