Am 20.07.2013 07:47, schrieb Josh Triplett: > Package: udev > Version: 204-1 > Severity: normal > > Since upgrading from udev in unstable to udev 204-1 in experimental, > /dev/rfkill no longer gets the correct permissions. gnome-shell's > bluetooth icon says: > > (gnome-shell:2228): Bluetooth-WARNING **: Could not open RFKILL control > device, please verify your installation > > Sure enough: > > ~$ ls -l /dev/rfkill > crw-r--r-- 1 root root 10, 59 Jul 19 22:20 /dev/rfkill > > I'd guess that the new version of udev broke > /lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules:
61-gnome-bluetooth-rfkill.rules tags the rfkill device for both ConsoleKit (udev-acl) and logind (uaccess). Since you are not using logind (I see from your other bug reports, that you have libpam-systemd not installed, which you should install btw!), logind will not apply proper ACLs for that device, so you have to rely on ConsoleKit for applying the ACL. For ConsoleKit, you need to upgrade to the version in experimental. The udev-acl tool was moved out of udev into ConsoleKit. The next udev upload will have a corresponding breaks in udev. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
