Network Manager not allowing user to control connections

English Network/Internet
1

Upgraded this machine from 13.2 using DVD upgrade

Network Manager 1.0.6-12 from OSS installed and controlling network.
I am a member of groups **users daemon tty lp dialout cdrom at vboxusers sshd systemd-journal plugdev
**
I am connecting to WiFi, but NM reports I am not authored to disconnect one and connect to another

Form search, I suspect a polkit issue, but don’t want to mess things up, so ask first, then make change

2

Probably the issue with the polkit update to 0.113?
I.e. it should work if you login after boot, but you’ll not have sufficient privileges if you logout and login again.

AFAIK, Leap 42.1 shipped with polkit 0.112 and got 0.113 as update (like 13.2), so you should be able to revert the package back to the previous version using the “Versions” tab in YaST.

OTOH, if you installed the polkit update and did not reboot since then, this might be the cause for your problem too.

3

I did get the 42.1 pollkit 0.113 update, but several days and a least a couple reboots since then.
I can’t honestly remember if I tried to change hotspots recently, so may have been in this state for a few days.

I did make changes to bluetooth (bluedevil to bluedevil5) today, perhaps that tweaked pollkit.

At any rate, just to be sure, I rebooted just now and I am back in control of NM and my WiFi choices.

Thanks

4

Yeah, on first login after a reboot, it should work as mentioned.
The problem only manifests if logging out and in again, it seems.

See 954139 – polkit 0.113-6.1 creates unnecessary password prompt on login
(the problem also exists in 13.2 since the update to polkit 0.113 there)

5

I don’t know if you’re seeing what I just saw…

The setup and events leading up to losing ability to manage network connections is different…

I have a LEAP/LXDE machine that initially managed its connections using wicked, then I switched over to NM
Then I installed Enlightenment and MATE Desktops and everything seemed to go well.
But, when I moved to a different network, I found that when I opened the gnome applet “Network Connections” which LXDE uses as a frontend to NM, the previously configured network connection had disappeared and each attempt to create a new connection resulted in an error, something like “User 1000 session not found”

Same thing when logged in as a normal User in any Desktop.
But, when I logged in as root, the gnome Network Connections applet displayed the previously missing network connection and I was able to configure a new connection (of course also configured connection to apply for all Users).

So, bottom line is that somehow (In my case there were too many changes happening to pinpoint which was the cause) that the security context of NM changed and is no longer running by default with sufficient (root) permissions.

Would have been interesting if you had also tried to login as root and been able to configure network connections.

TSU

6

While id did sort of follow your path from Wicked to NM for network control, all my action was with KDEPlasma 5.

My conclusion was that my issue was induced by the pollkit issue raised by Wolfi, a full reboot return my user control of NM.

So no, I did not try root.

I have seen no polkit updates since that event. I do rather frequently end up logging out and logging in without reboot
Plasma5 freezes or crashes occasionally, my easy out is alt+ctrl+backspace+backspace to kill the GUI and get back to greeter.
Last night I received a popup requiring root authorization to enter S3 (sleep), which I am assuming is also related to polkit.

7

No, but a testing package is available in the bug report since a few hours:
https://bugzilla.opensuse.org/show_bug.cgi?id=954139#c6

If people confirm that it’s working, it will probably be released as update ASAP.

8

Cool, I’ll give it a try

9

Hmm, downloaded the RPM, but YAST sez:

#### YaST2 conflicts list - generated 2015-11-17 09:27:48 ####

nothing provides libpolkit0 = 0.113-9.1 needed by polkit-0.113-9.1.x86_64

     ] do not install polkit-0.113-9.1.x86_64

     ] break polkit-0.113-9.1.x86_64 by ignoring some of its dependencies

#### YaST2 conflicts list END ###
10

Try to choose “break polkit…”.

If you have an OBS account and/or osc installed, you could also download the updated libpolkit0 rpm from the home:msmeissn:branches:openSUSE:Leap:42.1:Update/polkit.openSUSE_Leap_42.1_Update project.

11

I tried break polkit, the proposed fix
polkit-0.113-9.1.x86_64.rpm is installed.

The current session lock up fairly quickly, I killed GUI back to greeter, logged in and appears to be working correctly.

I’ll put a few minutes in on it then comment to bug

12

the fix still lookin’ good after 30 minutes of use

13

I resolved my problem, and my guess is my solution should work for you, too.

I discovered that anything short of a complete system re-install didn’t force system policy to be corrected.

Run the following, and depending on how many packages you already have cached on your system you may have your problem fixed within 15 minutes

zypper dup

HTH,
TSU

14

Thanks, Tsu.

So far, just installing the bugfix RPM and rebooting has worked for me, but then I am not using it intensively.

I assume the zupper dup backed out the upgrade for you?
Or, perhaps the upgrade rpm did not fully install itself in the firstplace?

15

No,
With the “new” target (not original “old”) repos configured, it re-installs the “new” system.

In retrospect,
What you did likely only installed the config file and/or new settings (Yes, I’m guessing) and “zypper up” should have done the same thing.

But, if you’ve run “zypper up” which IMO is simpler than installing a particular package unless the new package isn’t an ordinarily installed package then the problem is likely functional and not simply an incorrect setting.

“zypper dup” ensures that everything that’s necessary should be installed, present and configured correctly without sleuthing the exact issue.

TSU