Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Blueman on startup asks for authentication twice

I installed Blueman to setup my Bluetooth mouse, and it seems to work all fine, though, when I start Fedora, it asks me to enter my password twice, once to authenticate to network or something and the other time for changing the Rfkill state. This can be a bit annoying, and I want to make sure that the authentications on startup do not appear.

I made the following edits, but it still appears:

/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules:

# /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/bin/hciconfig %k up"

/etc/polkit-1/rules.d/81-blueman.rules:

# /etc/polkit-1/rules.d/81-blueman.rules

# Rule to relax polkit and remove the two auth steps on startup
polkit.addRule(function(action, subject) {
    if (action.id == "org.blueman.rfkill.setstate" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
    if (action.id == "org.blueman.network.setup" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
});

Any ideas how can I overcome the authentication checks at startup?

Blueman on startup asks for authentication twice

I installed Blueman to setup my Bluetooth mouse, and it seems to work all fine, though, when I start Fedora, it asks me to enter my password twice, once to authenticate to network or something for configuring the network, and the other time for changing the Rfkill state. RfKill State. This can be a bit annoying, and I want to make sure that the authentications on startup do not appear.

I made the following edits, but it still appears:

/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules:

# /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/bin/hciconfig %k up"

/etc/polkit-1/rules.d/81-blueman.rules:

# /etc/polkit-1/rules.d/81-blueman.rules

# Rule to relax polkit and remove the two auth steps on startup
polkit.addRule(function(action, subject) {
    if (action.id == "org.blueman.rfkill.setstate" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
    if (action.id == "org.blueman.network.setup" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
});

Any ideas how can I overcome the authentication checks at startup?

Blueman on startup asks for authentication twice

I installed Blueman to setup my Bluetooth mouse, and it seems to work all fine, though, when I start Fedora, it asks me to enter my password twice, once for configuring the network, and the other time for changing the RfKill State. This can be a bit annoying, and I want to make sure that the authentications on startup do not appear.

I made the following edits, but it still appears:

/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules:

# /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/bin/hciconfig %k up"

/etc/polkit-1/rules.d/81-blueman.rules:

# /etc/polkit-1/rules.d/81-blueman.rules

# Rule to relax polkit and remove the two auth steps on startup
polkit.addRule(function(action, subject) {
    if (action.id == "org.blueman.rfkill.setstate" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
    if (action.id == "org.blueman.network.setup" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
});

I basically see the following lines in my logs once I loggin and enter the passwords:

Nov 10 15:40:55 vt.io polkitd[1248]: Operator of unix-session:2 successfully authenticated as unix-user:eyt to gain TEMPORARY authorization for action org.blueman.network.setup for system-bus-name::1.333 [/usr/bin/python3 /usr/bin/blueman-applet] (owned by unix-user:eyt)
Nov 10 15:40:57 vy.io polkitd[1248]: Operator of unix-session:2 successfully authenticated as unix-user:eyt to gain TEMPORARY authorization for action org.blueman.rfkill.setstate for system-bus-name::1.333 [/usr/bin/python3 /usr/bin/blueman-applet] (owned by unix-user:eyt)
Nov 10 15:41:26 vt.io audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Any ideas how can I overcome the authentication checks at startup?

Blueman on startup asks for authentication twice

I installed Blueman to setup my Bluetooth mouse, and it seems to work all fine, though, when I start Fedora, it asks me to enter my password twice, once for configuring the network, and the other time for changing the RfKill State. This can be a bit annoying, and I want to make sure that the authentications on startup do not appear.

I made the following edits, but it still appears:

/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules:

# /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/bin/hciconfig %k up"

/etc/polkit-1/rules.d/81-blueman.rules:

# /etc/polkit-1/rules.d/81-blueman.rules

# Rule to relax polkit and remove the two auth steps on startup
polkit.addRule(function(action, subject) {
    if (action.id == "org.blueman.rfkill.setstate" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
    if (action.id == "org.blueman.network.setup" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
});

I basically see the following lines in my logs once I loggin and enter the passwords:passwords on startup:

Nov 10 15:40:55 vt.io polkitd[1248]: Operator of unix-session:2 successfully authenticated as unix-user:eyt to gain TEMPORARY authorization for action org.blueman.network.setup for system-bus-name::1.333 [/usr/bin/python3 /usr/bin/blueman-applet] (owned by unix-user:eyt)
Nov 10 15:40:57 vy.io polkitd[1248]: Operator of unix-session:2 successfully authenticated as unix-user:eyt to gain TEMPORARY authorization for action org.blueman.rfkill.setstate for system-bus-name::1.333 [/usr/bin/python3 /usr/bin/blueman-applet] (owned by unix-user:eyt)
Nov 10 15:41:26 vt.io audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Any ideas how can I overcome the authentication checks at startup?

Blueman on startup asks for authentication twice

I installed Blueman to setup my Bluetooth mouse, and it seems to work all fine, though, when I start Fedora, it asks me to enter my password twice, once for configuring the network, and the other time for changing the RfKill State. This can be a bit annoying, and I want to make sure that the authentications on startup do not appear.

I made the following edits, but it still appears:

/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules:

# /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/bin/hciconfig %k up"

/etc/polkit-1/rules.d/81-blueman.rules:

# /etc/polkit-1/rules.d/81-blueman.rules

# Rule to relax polkit and remove the two auth steps on startup
polkit.addRule(function(action, subject) {
    if (action.id == "org.blueman.rfkill.setstate" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
    if (action.id == "org.blueman.network.setup" && subject.local && subject.active && subject.isInGroup("wheel")) {
        return polkit.Result.YES;
    }
});

I basically see the following lines in my logs once I enter the passwords on startup:

Nov 10 15:40:55 vt.io polkitd[1248]: Operator of unix-session:2 successfully authenticated as unix-user:eyt to gain TEMPORARY authorization for action org.blueman.network.setup for system-bus-name::1.333 [/usr/bin/python3 /usr/bin/blueman-applet] (owned by unix-user:eyt)
Nov 10 15:40:57 vy.io polkitd[1248]: Operator of unix-session:2 successfully authenticated as unix-user:eyt to gain TEMPORARY authorization for action org.blueman.rfkill.setstate for system-bus-name::1.333 [/usr/bin/python3 /usr/bin/blueman-applet] (owned by unix-user:eyt)
Nov 10 15:41:26 vt.io audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Any ideas how can I overcome the authentication checks at startup?

EDIT:

Apparently, I saw the following error:

Nov 10 16:03:35 vt.io polkitd[1117]: Error compiling script /etc/polkit-1/rules.d/81-blueman.rules

It is defined as shown above, and has the following permissions:

-rw-r--r--. 1 root root 411 Nov 10 15:39 81-blueman.rules

Any reason why the compilation may fail?