Right now stuff like the uaccess tag are applied to all rfkill directories, including /sys/modules/rfkill, which is quite broken. The udev rule should be tightened to actually apply the uaccess only to the device node device, and nothing else.
Can you do the necessary changes, or at least propose here how you expect the rule to look ?
Kay, can you suggest a good udev config line to Matthias?
I guess the entire content of the file can be replaced with:
KERNEL=="rfkill", SUBSYSTEM=="misc", TAG+="uaccess"
I would do the change, but I don't have any bluetooth devices to test this with.
gnome-bluetooth-3.1.4-3.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-bluetooth-3.1.4-3.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
gnome-bluetooth-3.1.92-1.fc16 has been submitted as an update for Fedora 16.
gnome-bluetooth-3.2.0-1.fc16 has been submitted as an update for Fedora 16.
gnome-bluetooth-3.2.0-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
I see incorrect permissions on the /dev/rfkill device with 3.2.1-2 where perms are 644 and owner is root. Using this UDEV rule corrects the issue:
You probably just need the rule in:
Systemd systems do not use udev-acl.