Control: retitle -1 gnome-bluetooth: various segfaults seen when /dev/rfkill
cannot be opened
Control: reassign -1 gnome-bluetooth 3.4.2-1
Control: tags -1 + moreinfo
Summary of bug report: in Debian 7 'wheezy', Bluetooth-related processes
(bluetooth-wizard, bluetooth-applet, gnome-control-center) were seen to
crash with a segmentation fault if the user is not logged in at a tty.
This warning seems to be correlated with the crash:
Bluetooth-WARNING **: Could not open RFKILL control device, please verify your
installation
Does this still happen in a more current version of Debian?
Looking at the backtrace, I suspect this was a bug in
libgnome-bluetooth10, which has been renamed to libgnome-bluetooth13
in Debian 8 'jessie' and newer releases. I've reassigned the bug to the
gnome-bluetooth binary package (which comes from the same source package
anyway) to cover both possibilities.
On Mon, 17 Jun 2013 at 18:49:20 +0900, Takashi Yano wrote:
> The permission of /dev/rfkill is changed.
> When the user do not login in console, it is:
> crw-r--r-T+ 1 root root 10, 59 Jun 17 16:00 /dev/rfkill
>
> When the user login in console, it is:
> crw-rw-r-T+ 1 root root 10, 59 Jun 17 16:00 /dev/rfkill
To see the permissions that are effective for your user, you would have
to use the command "getfacl /dev/rfkill":
$ getfacl /dev/rfkill
getfacl: Removing leading '/' from absolute path names
# file: dev/rfkill
# owner: root
# group: root
user::rw-
user:smcv:rw-
group::rw-
mask::rw-
other::r--
Regards,
smcv
