https://bugs.kde.org/show_bug.cgi?id=359842
Neil Rickert <nrick...@ameritech.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nrick...@ameritech.net
--- Comment #14 from Neil Rickert <nrick...@ameritech.net> ---
In my opinion, this should be reopened. I won't reopen because of comment 8,
but I disagree with that comment.
Firstly, this is specifically a plasma 5 issue. If the network connect is
setup in Gnome or XFCE or MATE or LXDE, then the problem does not arise. If
"nm-applet" is used as network client and the connection is setup with that
client, the problem does not arise. When I tried running nm-applet in Plasma
5, I could not access it, so nm-applet has to be run elsewhere.
Since it works with nm-applet (which is used in XFCE), then it cannot be a
polkit problem. Rather, the plasma client does things differently and, in my
opinion, wrongly.
I have a blog post about this at:
https://nwrickert2.wordpress.com/2016/01/06/another-look-at-networkmanager-and-tumbleweed/
Responding to comment 4
>I think that "org.freedesktop.NetworkManager.settings.modify.system" = "auth"
>is responsible for your problem.
Yes, that's possible. But that's the wrong polkit rule. The user is just
making a connection. The user is not changing a system connection. In my
opinion, it should instead use
"org.freedesktop.NetworkManager.network-control". As far as I know, it is a
plasma issue to specify the appropriate rule.
When the user first changed the connection to be a system connection, then
"modify.system" was appropriate. But just connecting to an existing system
connection does not modify the connection definition, so should be under the
more general "network-control".
--
You are receiving this mail because:
You are watching all bug changes.
