Oops, sorry! I think now ‘org.freedesktop.NetworkManager.enable-disable-wifi’ is for the “Enable Wireless” checkbox in the NetworkManager applet.
Maybe the right one would be ‘org.freedesktop.NetworkManager.use-user-connections’. This one is not available in /usr/share/polkit-1/actions. But it is in /etc/polkit-1/rules.d/90-default-privs.rules…
Since you folks talked me into to sticking with systemD, I decided to read about it.
The problem appears to have arisen because I was booting into run level 2 and then having root start kdm for X.
Instead one must:
>systemctl isolate runlevel5.target
in order to start all of the various processes including kdm, then everything works. This became clear as all of you led me through the various files that determine permissions.
Incidentally, my system resides entirely on a 500 GB portable “Passport” USB drive. It is fully encrypted with root and home partititions in a LV and the boot directory on its own separate unencrypted partition. When at home I plug it into my home machine. When at work plug it into my office machine. In fact it will run any 64 bit machine. I’ve been doing this since Opensuse 11.1. In the past I was even able to install the proprietary NVIDIA driver, which loaded automatically when the appropriate hardware was present. With 12.3 the proprietary drivers don’t seem to be necessary. I had to install Opensuse 12.3 to replace 11.3 which could no longer deal with Verizon’s DSL.
So maybe polkitd wasn’t even running?
That would explain why changing the privileges had no effect…rotfl!
Well, glad you found the problem!
Just to finish this off:
I tried that and yes, those are really the policy action rules that affect this.
Also, changing them in the KDE systemsettings module did have effect (immediately, I didn’t even have to log out)
You just have to change the right rules, of course… Btw., the authorization dialog does show the rule which causes to ask for the password. Just click on the “Details” button.
One thing I don’t quite understand yet, is how the default privileges are supposed to work.
If I call “set_polkit_default_privs” those actions in /usr/share/polkit-1/actions aren’t touched at all and still remain active as they were set.
But anyway…
One thing I don’t quite understand yet, is how the default privileges are supposed to work.
If I call “set_polkit_default_privs” those actions in /usr/share/polkit-1/actions aren’t touched at all and still remain active as they were set.
But anyway…
No, the active (pkla) policy files reside in /var/lib/polkit-1/localauthority/10-vendor.d/
The KDE settings module clearly shows the latter and I am not asked for a password, so this is the one that seems to be active…
And what about /etc/polkit* and set_polkit_default_privs? They didn’t seem to change /var/lib/polkit-1/localauthority/10-vendor.d/ either… Only /etc/polkit-1/rules.d/90-default-privs.rules
:\
Well, and “systemctl status polkit.service” tells me:
May 02 12:33:24 amiga polkitd[10805]: Started polkitd version 0.110 May 02 12:33:24 amiga polkitd[10805]: Loading rules from directory /etc/polkit-1/rules.d
May 02 12:33:24 amiga polkitd[10805]: Loading rules from directory /usr/share/polkit-1/rules.d
May 02 12:33:24 amiga polkitd[10805]: Finished loading, compiling and executing 2 rules
So nothing gets loaded from /var/lib/polkit-1/localauthority/ …
What role does this play then?
I only found it being mentioned in the pklocalauthority man page from polkit-0.105. But that’s not there any more in v0.110 included in oS12.3…