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:

~$ cat /lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules
# Set ACLs for console users on /dev/rfkill
# This is necessary until a daemon can properly handle access to the 
# kill switch
# http://bugs.debian.org/563902
# https://bugzilla.redhat.com/show_bug.cgi?id=514798

# logind
# https://bugzilla.redhat.com/show_bug.cgi?id=733326
KERNEL=="rfkill", SUBSYSTEM=="misc", TAG+="uaccess"

# ConsoleKit
ENV{ACL_MANAGE}=="0", GOTO="gnome_bluetooth_end"
ACTION!="add|change", GOTO="gnome_bluetooth_end"
KERNEL=="rfkill", SUBSYSTEM=="misc", TAG+="udev-acl"
LABEL="gnome_bluetooth_end"


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udev depends on:
ii  debconf [debconf-2.0]  1.5.50
ii  libacl1                2.2.52-1
ii  libblkid1              2.20.1-5.5
ii  libc6                  2.17-7
ii  libkmod2               9-3
ii  libselinux1            2.1.13-2
ii  libudev1               204-1
ii  lsb-base               4.1+Debian12
ii  procps                 1:3.3.8-2
ii  sysv-rc                2.88dsf-43
ii  util-linux             2.20.1-5.5

udev recommends no packages.

udev suggests no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to