SUMMARY Apply button in Wireguard VPN connection editor is always inactive. STEPS TO REPRODUCE 1. Add Wireguard VPN, restart systemsettings (just in case) 2. Edit something in connection editor for added VPN (e.g. automatic connection priority) 3. Try to save changes by clicking apply OBSERVED RESULT Changes can't be saved because apply button remains inactive. EXPECTED RESULT Changes are saved. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION
I can confirm this is still not fixed. The only workaround I found, is to edit the connection name of the VPN connection. Then the apply button becomes active again. Operating System: Manjaro Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 5.19.17-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6800 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B46 System Version: 1.0
I've been running into this myself: Operating System: EndeavourOS KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.3-zen1-2-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C95 System Version: 1.0
STEPS TO REPRODUCE 1. Edit a WireGuard connection in network connection settings 2. Open 'Peers...' menu 3. Change something, for example adding a network to 'Allowed IPs' 4. Press 'OK' OBSERVED RESULT The 'Apply' button remains grayed out. Settings are not saved. Closing settings gives no warning that settings are not saved. After re-opening settings, the previous settings are shown. EXPECTED RESULT Settings should be applied when clicking 'OK', or clicking 'Apply' should be allowed to save it then. Closing settings should give a warning that there are unsaved pending changes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 39 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION I suspect this downstream report, submitted a few months ago, describes the same issue: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661
*** Bug 476581 has been marked as a duplicate of this bug. ***
I have been running into same problem on Debian 12 Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.5.0-0.deb12.4-amd64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7640U w/ Radeon 760M Graphics Memory: 30,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A5
This is still an issue on Plasma 6 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland
This has been an issue for a while now so I thought I'd dig a little deeper - especially since this only happens on some of my WireGuard connections. This is the in all of my WireGuard connections that I can't modify using the GUI: [ipv6] address1=bla::bla/128 method=manual And this is in all of the configurations where I can: [ipv6] method=disabled So, disabling IPv6 for the connection and reloading NetworkManager causes the bug to disappear and the apply button works. The bug seems related to IPv6 settings. I hope this helps with solving the issue!
Still an issue on Plasma 6.1.2 I want to disable automatic connection to the VPN profile on startup, but there's no way to do it, and I can't figure out how to disable it via nmcli either.
(In reply to sashok.olen from comment #8) > Still an issue on Plasma 6.1.2 > I want to disable automatic connection to the VPN profile on startup, but > there's no way to do it, and I can't figure out how to disable it via nmcli > either. Slightly off topic, but in case anyone else runs into this exact scenario (common as auto-connect is on by default), the command is: nmcli con mod [connection_name] connection.autoconnect false
I would like to confirm that this is still an unfixed issue on 6.1.4. Quite an annoying bug.
*** Bug 458746 has been marked as a duplicate of this bug. ***
There seem to be quite some issues with the IPv6 support for the Wireguard settings via the KCM: Added addresses (bug 453453) or routes (something I ran into) are not persisted even though the Apply button is not greyed out those cases. I guess that bug 461319 is related as well even though it doesn't mention IPv6.
Work-around in command line: `nmcli con mod <connection-name> connection.autoconnect no`
Ran across this issue today, i know the bug states its only when ipv6 is configured but I don't have anything under my ipv6 tab and it's an issue for me.
I feel like people have misinterpreted the root cause. For me it's every other opening of the connection when t's impossible to save. Steps: 1. Click on wireguard connection 2. Changes are saveable 3. Click on a wifi connection and click on the wireguard connection again 4. Changes are not saveable 5. Do step 3 again 6 Changes are saveable again
Updating the title as, at least on my Fedora KDE 42 device with Plasma from git master, my experience mirrors Antti's, and occurs even if IPv6 hasn't been set to disabled. Thanks!