Description of problem: As of 1/19/2006 the hcid daemon won't start unless the enforcing=0. Version-Release number of selected component (if applicable): bluez-utils-2.22-2.1 selinux-policy-2.1.13-1 selinux-policy-targeted-2.1.13-1 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: hcid doesn't start and I cannot use bluetooth devices Expected results: hcid starts Additional info:
This still occurs with: selinux-policy-2.2.9-2 selinux-policy-targeted-2.2.9-2
audit2why tells me: type=AVC msg=audit(1138959953.541:158): avc: denied { read } for pid=3448 comm="hid2hci" name="001" dev=tmpfs ino=3564 scontext=user_u:system_r:bluetooth_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file audit2allow tells me: allow bluetooth_t device_t:chr_file read;
Me too. hcid bombs out with: Mar 24 15:15:28 localhost hcid[18217]: Bluetooth HCI daemon Mar 24 15:15:28 localhost hcid[18217]: Can't get system message bus name: Connection ":1.16" is not allowed to own the service "org.bluez" due to SELinux policyMar 24 15:15:28 localhost hcid[18217]: Unable to get on D-BUS
On released FC5, I get the same /var/log/messages entries about hcid as above, but the only audit messages I see are about bluez-pin, not hcid.
Please re-open and file against selinux-policy is this is still happening.