LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Blueman requires authentication twice when logging into account (https://www.linuxquestions.org/questions/fedora-35/blueman-requires-authentication-twice-when-logging-into-account-4175626708/)

Neyzan 03-31-2018 01:37 AM
Blueman requires authentication twice when logging into account
 
When I log into my user account Blueman asks twice for authentication. First with the message "Networking requires privileges" and then with the message "Setting Rf Kill State requires privileges".
I'm trying to find a way to have my user authenticated by default, which I'm assuming can be done by adding the user to some group, but I cannot seem to find which one. "lp" group was suggested by some posts, but my user is added to that one and the double authentication (triple, if you count the original login to the user account) persists.
An option could always be to deactivate authentication for Blueman entirely and for all users, but I would prefer to avoid that.

I'm using Fedora 27 with LXQt 0.11.1.

voleg 04-04-2018 05:00 AM
Been there.
Add yourself to "wheel" group. Probably you've already did that for other reason.
Then create new file /etc/polkit-1/rules.d/81-blueman.rules with follwing content:
Code:
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;
  }
});
If you do not want make deal with wheel, fix code to other group name.

Neyzan 04-08-2018 08:27 AM
@voleg, thanks! this did indeed solve the issue.

Now I have another issue with blueman, since the kernel 4.15.14 upgrade, you can see it here.

thecarlosfilipe 09-01-2018 02:43 PM
Quote:
Originally Posted by voleg (Post 5839201)
Been there.
Add yourself to "wheel" group. Probably you've already did that for other reason.
Then create new file /etc/polkit-1/rules.d/81-blueman.rules with follwing content:
Code:
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;
  }
});
If you do not want make deal with wheel, fix code to other group name.

Hello, @voleg! I would just like to thank you for your tip too. I had the same problem and thanks to your help I was able to solve it here. Thanks!

jurkomp 05-16-2021 03:48 AM
The same problem in new Debian Buster
 
Few days ago I have upgraded from 4.19.0-10 to 4.19.0-16 and suddenly the same problem has appeared.
After some googling and browsing through config files I have discovered that the problem can be solved by
adding the user to: "netdev" group.


All times are GMT -5. The time now is 06:31 PM.