System policy prevents modification of network settings for all users

This problem popped up after updating a 13.2 netbook (HP 110-1116), … and it just happened on a new 42.1 installation on a newer model netbook (HP 110-3032).

I was surprised to see no search hits on the issue here. … and could not come with any good leads searching elsewhere.

Since this seems to be a common issue that crept in sometime in late 13.2, it seems like a good idea to get a solution on the record for others with the same problem?

Be happy to forward dmesg, lspci, & working iwconfig or any other test results.

TIA & Happy Holidays to all!!

Lee

i think you would need to give a much detailed explanation of what you are doing and what is the problem that you are encountering. Then someone will step up and try to offer solutions or ask for more details to help get a solution. good luck

Don’t know what to add, … the problem is in the subject - when starting or resuming both of these netbook systems, a message box pops up titled:

“System policy prevents modification of network settings for all users”, and must be dismissed before logging in or resuming the session. [Neither dismiss or authorize makes any difference in functionality.]

Cannot find anything in the Forums, … but there are number of mentions for Ubuntu - unfortunately, none of those fixes work.

I have more data available, but, for some reason, attachments are disabled.

TFTR!

Lee

To me, this sounds a bit like the polkit bug that affected NetworkManager. But it has already been fixed.

I don’t know if that is the problem. Your description lacks sufficient details.

What details would you like? Attachments are not allowed, … where can I post dmesg, lspci, and an iwconfig?

TFTR!

Lee

Are you using NetworkManager or wicked for the network?

What desktop are you using (KDE/Plasma 5, or Gnome or XFCE or something else)?

Do you connect to the network via ethernet or WiFi?

What version of polkit is installed (you can use Yast Software Management to check).

Oh, you can post images and large files to susepaste (paste.opensuse.org), then provide a link.

Default installation, … config below:

> Are you using NetworkManager or wicked for the network?
>
Network Manager

> What desktop are you using (KDE/Plasma 5, or Gnome or XFCE or something else)?
>
Gnome

> Do you connect to the network via ethernet or WiFi?
>
Both; the problem only occurs on WiFi, however.

> What version of polkit is installed (you can use Yast Software Management to check).
>
0.113-9.1

> Oh, you can post images and large files to susepaste (paste.opensuse.org), then provide a link.
>
Thanks!!

Then it should not be the polkit problem that some people were having.

I am unable to reproduce the problem. I switched my laptop from “wicked” to “NetworkManager”, switched the login to use “gdm”, and then rebooted and logged into Gnome. I configured home WiFi. And it is working, except that I cannot find a Gnome option to change the MTU or to change the IPv6 privacy options.

Is there something non-standard that you are doing to your network connection, such as sharing it with all users or setting a non-default network property of some kind?

Also, changing the system security level to “secure” or “paranoid” will cause this even for modifying user connections.

What does this output?

grep SECURITY /etc/sysconfig/security

Simply in the post. Copy/paste the text (that is inclusing the prompt, the command and the next prompt) between CODE tags. You get the CODE tags by clicking on the # button in the tool bar of the post editor.

Example:

boven:~ # iwconfig
wlp0s29f7u5  IEEE 802.11bg  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          
enp1s8    no wireless extensions.

lo        no wireless extensions.

boven:~ # 

I also suffer this problem for a while. After 13.2 to Leap42.1, laptop, just after every time booting up, connecting to wifi, this occurs.
I checked:


       eric@laptop:~> grep SECURITY /etc/sysconfig/security 
PERMISSION_SECURITY="easy local"
# PERMISSION_SECURITY. If PERMISSION_SECURITY contains 'secure' or
     

I don’t know what does this mean?

 grep SECURITY /etc/sysconfig/security
# PERMISSION_SECURITY. If PERMISSION_SECURITY contains 'secure' or
PERMISSION_SECURITY="easy local"

The main people who are having problems similar to this are using KDE. And they were not having problems back in December – only in the last week or two.

However there is one special. If you configure the network under KDE, and then switched to using Gnome, then you probably would run into problems. If you configured with KDE under opensuse 13.2, then upgraded your system to 42.1 and Gnome, you might run into problems.

Can you tell us whether either of these circumstances applies?

I just noticed that you are a new commenter to this thread, and not the initiator. It is often better to start your own thread to avoid confusion.

In any case, what desktop are you using? KDE behaves differently from Gnome or XFCE with network settings.

Hi,

(Family using the OpenSUSE - wife, son e me)


gilbertoca@linux-s6k1:~$ cat /etc/os-release 
NAME="openSUSE Leap"
VERSION="42.1"
VERSION_ID="42.1"
PRETTY_NAME="openSUSE Leap 42.1 (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:42.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"


After installing the OpenSUSE leap 42.1 (kde now 5.5.1 version) I’ve struggled with wifi not saving the password problem [1]. Practically everyone said: You can check “All users may connect to this network” in General Settings. It led to another problem, this one of course! [2] . We have no choice, either put the wifi password (setting up it again and again) or put the root password and wait the nm establish the network.


gilbertoca@linux-s6k1:~$ grep SECURITY /etc/sysconfig/security
PERMISSION_SECURITY="easy local"
# PERMISSION_SECURITY. If PERMISSION_SECURITY contains 'secure' or


I don’t want to install another DE - I love KDE!
So, it deserves a bug report?

Regards,

PS.: Another thing that takes me on crazy is the hidden authentication dialog syndrome [3]. Can you see it? It always hidden.

[1] https://www.google.com.br/search?q=OpenSuse+does+not+even+remember+the+wifi+password.&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&ei=hWmCV_KVE-yp8wfAn6Mo
[2] https://dl.dropboxusercontent.com/u/9093640/System%20policy%20prevents%20modification%20of%20network%20settings%20for%20all%20users.png
[3] https://dl.dropboxusercontent.com/u/9093640/It%20always%20hidden.png

As far as I know, it is fixed.

In KDE:

Edit connections in NetworkManager.
Select the particular connection of concern to edit.
Go the the Security tab. Look for the place where you enter the network key.

Next, maximize the edit window. Or if it is already maximized, the unmaximize it. (The need to do this is a different but).

Toward the right of the space where you enter the key, there should be two icons to click. One of them allows you to select where to save the password. As I recall, the options are: in the user settings, unencrypted system settings, enter the password every time. Choose the unencrypted system settings (the wording might be a little different). You probably still need to enter the network key in that slot. Save the changes. And, thereafter, you should be set.

Did it some times and I could/can see only one icon [1].

For me it is another hidden feature. :wink: [2]
The unencrypted system settings finally works.

Thanks a lot!

[1] https://dl.dropboxusercontent.com/u/9093640/Screenshot_20160710_162048.png
[2] https://dl.dropboxusercontent.com/u/9093640/Screenshot_20160710_162218.png

Great. And thanks for reporting back, as that helps other users.

That’s why you should maximize/unmaximize or resize the dialog, that makes the second icon appear.
When the dialog is opened, the icons are above each other.

That’s a bug in Qt 5.5, fixed in 5.6.

For me it is another hidden feature. :wink: [2]

It’s exactly the same behavior as in NetworkManager’s “official” frontend, nm-applet.