Switching bluetooth on/off with gnome bluetooth applet

English Hardware
#1

Hi!

On my ASUS Eee 1000H with openSUSE 11.3 I’d like to be able to switch bluetooth on and off with the gnome bluetooth applet.

However, when I run /usr/bin/bluetooth-applet as a normal user, the applet tells me:


** (bluetooth-applet:8598): WARNING **: Could not open RFKILL control device, please verify your installation

Okay, so it doesn’t have write permissions on /dev/rfkill. When (as root) I change the permissions on /dev/rfkill from crw-r–r-- to crw-rw-rw-, the applet works as expected.
Until the next reboot, when the permissions for rfkill are reset to crw-r–r–. Can anybody here tell me how to make the permissions stick? Or if there is a better way to allow the applet to enable and disable the bluetooth adapter?

#2

Hi
I built on OBS eee-control for my eeePC 1000HE;
http://software.opensuse.org/search?q=eee-control&baseproject=openSUSE%3A11.3&lang=en&exclude_debug=true

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.3 (x86_64) Kernel 2.6.34-12-default
up 8 days 9:55, 2 users, load average: 0.10, 0.08, 0.02
GPU GeForce 8600 GTS Silent - Driver Version: 256.44

#3

Good to know, thanks! :slight_smile:

So that may solve the permission problem because the eee-control daemon runs with root privileges?

Still, no chance of using the gnome bluetooth applet? I’d like to stick with it… It strikes me as strange that it doesn’t work as expected (with a default system config, the applet doesn’t come up correctly because of the permission problem).

#4

So I installed your package (thanks again :)) - but that doesn’t make the issue go away (completely). I now have a nice tray icon for enabling/disabling various devices, among them bluetooth, as expected.
But still bluetooth isn’t completely switched on…

Before I switch on bluetooth rfkill list gives me the following:


# rfkill list
0: eeepc-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: eeepc-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: no

After using the eee-control applet to switch on bluetooth, I get:


0: eeepc-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: eeepc-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
7: hci0: Bluetooth
        Soft blocked: yes
        Hard blocked: no

What I get after setting the permissions on /dev/rfkill manually and then using bluetooth-applet to enable bluetooth (i.e.: when bluetooth works as expected) is:


0: eeepc-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: eeepc-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
8: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

Note that the device number for hci0 seems to change every time I switch it on and off.

I also read in various bug reports (on other distros) that I would need a 61-gnome-bluetooth-rfkill.rules file in /etc/udev/rules.d/, with the following content.


# Get access to /dev/rfkill for user
# See https://bugzilla.redhat.com/show_bug.cgi?id=514798
KERNEL=="rfkill",       ENV{ACL_MANAGE}="1"

Creating the file and then reloading the rules with

udevadm control --reload-rules

does… exactly nothing for me :frowning:

#5

Hi,
I have exactly the same problem. ACL is not set for /dev/rfkill, and so gnome-bluetooth-applet cannot access it for toggling bluetooth on/off. ACL support is set up in /etc/fstab for the root partition. I also can see, that there’s another device (/dev/video0) is set up with ACL.
I’m wondering, how Wifi is toggled by the Fn+F2 hotkey, which is working fine on my Asus EeePC 1000H. Isn’t this done by rfkill as well? When I was running Ubuntu on this netbook, I had to problems. There must be a solution,…:frowning:

#6

Hi dsengstock!

In case you still want to know a fix: The solution proposed in the bug I filed works for me:
https://bugzilla.novell.com/show_bug.cgi?id=632256

I.e.: create a file called 61-gnome-bluetooth-rfkill.rules file in /etc/udev/rules.d/ and put in it:


KERNEL=="rfkill", TAG+="udev-acl"

Reload udev rules with


udevadm control --reload-rules

List the permissions of /dev/rfkill with


la /dev/rfkill

If only root can write to the device, change that to your needs.
(e.g. chmod a+w /dev/rfkill, executed as root)

Now my bluetoothapplet works as expected :slight_smile: HTH