Description of problem: when trying out gnome really quick on my rawhide install i noticed: bluetooth-applet ** (bluetooth-applet:4496): WARNING **: Could not open RFKILL control device, please verify your installation -d doesnet show any more info... chmod 666 on /dev/rfkill makes it work as expected as non root user. Version-Release number of selected component (if applicable): gnome-bluetooth-2.30.0-1.fc14.x86_64 How reproducible: always
We install a rule (61-gnome-bluetooth-rfkill.rules) that should make the rfkill device available to the current user at the console. Can you reproduce that problem? What's the output of "ck-list-sessions" and "getfacl /dev/rfkill" when the problem happens? The content of the file: # Get access to /dev/rfkill for users # See https://bugzilla.redhat.com/show_bug.cgi?id=514798 KERNEL=="rfkill", ENV{ACL_MANAGE}="1"
Hi, Apologies in advance for barging on a Fedora bug, but I noticed the same problem in Debian, and tracked it down to an udev upgrade (rawhide seems to use the same version, 154). When I reported it as a bug the udev maintainer responded: "Other packages must not set ENV{ACL_MANAGE} (or the new tag which replaced it). gnome-bluetooth maintainer: for more information please discuss this on the linux-hotplug@vger mailing list." http://bugs.debian.org/582188
FWIW, this is the new rule Debian uses: http://svn.debian.org/wsvn/pkg-gnome/desktop/unstable/gnome-bluetooth/debian/61-gnome-bluetooth-rfkill.rules
(In reply to comment #2) > Hi, > > Apologies in advance for barging on a Fedora bug, but I noticed the same > problem in Debian, and tracked it down to an udev upgrade (rawhide seems to use > the same version, 154). When I reported it as a bug the udev maintainer > responded: > > "Other packages must not set ENV{ACL_MANAGE} (or the new tag which > replaced it). > gnome-bluetooth maintainer: for more information please discuss this > on the linux-hotplug@vger mailing list." > > http://bugs.debian.org/582188 Thanks, though I'd like to ask why a bluetoothd problem got added to the equation, given that it runs as root and should be able to access /dev/rfkill anyways. Fixed in gnome-bluetooth-2.30.0-2.fc14 (I double-checked that udev >= 154 wasn't in any other versions of the distribution either, to be sure). Did you already fix the problem for other packages that use ACL_MANAGE such as libmtp, or pilot-link?
(In reply to comment #4) > (I double-checked that udev >= 154 wasn't in any other versions of the > distribution either, to be sure). > > Did you already fix the problem for other packages that use ACL_MANAGE such as > libmtp, or pilot-link? This issue definitely bites pilot-link, filed bug #642435.