Bug 18165

Summary: "Edit Configuration" -> "allow all users to use this connection" doesn't stick
Product: Mageia Reporter: Frank Griffin <ftg>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: mageia, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: plasma-nm-5.6.2-1.mga6 CVE:
Status comment:
Bug Depends on:    
Bug Blocks: 17523    

Description Frank Griffin 2016-04-09 18:04:42 CEST
If you click on the applet tray icon, right-click on the top right icon, select "Configuration Edit", choose an interface (wireless in my case), click Edit in the TitleBar, and go to the General tab, there is a checkbox marked "allow all users to use this connection" (this used to be "this is a system connection).

If you check the box and click OK, the dialog closes with no error.  However, if you reopen the dialog, the box is unchecked again.

The older behavior when selecting "system" was that you would be prompted for the root password, and the "system" attribute would stick.

Without this, the /etc/NetworkManager/system-connections/{interface-name} file contains a "permissions=:user:xxx::" line which only activates the connection when user xxx logs on.  Removing this line causes the interface to be activated when NM starts.

This bug results in no network at runlevel 3 unless the particular user who first activated the interface logs on.  This, in turn, causes network mounts and the systemd remote-fs.target to fail during boot.
Comment 1 Marja Van Waes 2016-04-24 16:24:58 CEST
Assigning to all packagers collectively, since there is no maintainer for this package.

@ Frank

I guessed the version for the source package of plasma-applet-nm. Is it correct?

@ neoclust

You're the one who pushes plasma-nm most often. Is maintainer "nobody" correct?

CC: (none) => mageia, marja11
Blocks: (none) => 17523
Assignee: bugsquad => pkg-bugs
Source RPM: plasma-applet-nm => plasma-nm-5.6.2-1.mga6

Comment 2 Frank Griffin 2016-04-24 16:38:05 CEST
I'm not sure what version encountered the bug, but it appears to be fixed in the current version (the one you cited).

Status: NEW => RESOLVED
Resolution: (none) => FIXED