Arch Linux

Phoenix_the_II

Member

Registered: 2016-08-15

Posts: 2

plasma (& kde5) network manager edit connections save greyed out.

Hi,

Please follow me in this...

Add a wired connection using default options, thus dhcp and add this connection.

Then afterwards, you want to edit this connection at a later time to edit DNS servers. I add 8.8.8.8 in this IPV4 tab..

The "save" option stays greyed out.

Changing anything else, the save option stays greyed out...

(I can edit an openvpn connection perfectly fine)

(P.S., "nm-connection-editor" can edit things fine... but I want the KDE stuff to work properly, not some workaround.)

mum1989

Member

From: france

Registered: 2009-09-19

Posts: 50

Re: plasma (& kde5) network manager edit connections save greyed out.

same bug for me.

I edit some files in /etc/NetworkManager/system-connections but do nothing

it's this bug ? :
https://bugs.archlinux.org/task/42561

Last edited by mum1989 (2017-04-01 11:05:16)

kenchin

Member

Registered: 2013-02-12

Posts: 8

Re: plasma (& kde5) network manager edit connections save greyed out.

I'm encountering a similar issue whether using Connection editor version 5.9.4 (which uses NM version 1.6.2) or System Settings Module - Network Connections.

Oddly, for all Wi-Fi connections, the Save button in Connection editor as well as the Apply button in Network Connections will become clickable when I edit the IPv4 address.

but for Ethernet connections, the Save button in Connection editor as well as the Apply button in Network Connections remains grey out when I edit the IPv4 address.

Previously this was working fine.

xxdoctorhousexx

Member

Registered: 2016-05-30

Posts: 21

Re: plasma (& kde5) network manager edit connections save greyed out.

Hi everyone,

i see i am not alone reporting the same issue. I can create connections but i basically cannot modify any of them as the "apply" button is always greyed out.

here you can see

look at the "apply" button
apply button still grey

I perfectly remember it used to work in previous versions. I don't know what i am doing wrong. Has anybody got a solution/workaround?

thanks

whenov

Member

Registered: 2011-07-03

Posts: 10

Re: plasma (& kde5) network manager edit connections save greyed out.

I met the same problem.
For now you can use nmtui to edit the connections.

Last edited by whenov (2017-04-06 12:45:21)

kenchin

Member

Registered: 2013-02-12

Posts: 8

Re: plasma (& kde5) network manager edit connections save greyed out.

I have reported this bug: https://bugs.archlinux.org/task/53635

xxdoctorhousexx

Member

Registered: 2016-05-30

Posts: 21

Re: plasma (& kde5) network manager edit connections save greyed out.

Hello everyone,

a quick update, not sure it's relevant though... in the tab Wired of the selected wired network connection you can turn on the Apply button by flagging the allow auto-negotiation setting. From there you can then set the IP address to manual and it looks like it saves the configuration too. When you will reconnect to the network the Allow auto-negotiation flag will be reverted as it was before but your manual IP settings are saved and they seem to work.

hope it helps

grossws

Member

Registered: 2015-06-24

Posts: 3

Re: plasma (& kde5) network manager edit connections save greyed out.

Another workaround (without installing nm-connection-editor) is to use connections settings via systemd setting.

Apply button works fine there and connection settings are updated.

UPD: workaround seems to be unstable. I couldn't figure out when it works and when it doesn't.

Last edited by grossws (2017-04-13 00:54:25)

kenchin

Member

Registered: 2013-02-12

Posts: 8

Re: plasma (& kde5) network manager edit connections save greyed out.

I have reported this bug upstream: https://bugs.kde.org/show_bug.cgi?id=378744

zaxdan69

Member

Registered: 2016-06-04

Posts: 273

Re: plasma (& kde5) network manager edit connections save greyed out.

I just found that I have the same problem(I think kde updated some days ago). @xxdoctorhousexx workaround works though. But the bug is still there