Bug 499675

Summary: Wireguard settings cannot be changed (myabe others aswell)
Product: [Applications] systemsettings Reporter: wilfred
Component: kcm_networkmanagementAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: jgrulich
Priority: NOR    
Version First Reported In: 6.1.5   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: kde version

Description wilfred 2025-02-08 11:29:30 UTC
Created attachment 178072 [details]
kde version

SUMMARY
Changing a wireguard connection does not work as the apply button remains greyed out

STEPS TO REPRODUCE
1. add new wireguard connection
2. save the newly created connection
3. change any setting that requires applying (private key or ipv4 settings for example)
4. see the apply button being greyed out

OBSERVED RESULT

Apply button is not enabled by changing settings

EXPECTED RESULT
Apply button being enabled and settings are allowed to be saved, alternatively i expect a warning that the (new) configuration cannot be saved because ... < insert reason like "file permissions are too restrictive"

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
seems related to https://bugs.kde.org/show_bug.cgi?id=493643 other than that i run the latest kde on ubuntu
Comment 1 Bug Janitor Service 2025-02-08 11:33:36 UTC
Thank you for the bug report!

However Plasma 6.1.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27. (LTS), and 6.2 (non-LTS) or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need support for Plasma 6.1.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report.