Bug 425301

Summary: System Settings do not save/read manually proxy settings
Product: [Applications] systemsettings Reporter: s.moosbauer
Component: kcm_proxyAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns, laurentlepoittevin, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.19.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description s.moosbauer 2020-08-13 14:03:33 UTC 
SUMMARY
When setting a proxy manually the kioslaverc file is written correctly but the GUI does not show the settings after reopening System Settings -> Proxy. Even if System Settings remain open but another settings tab is opened the settings for the proxy disappear when resuming to proxy settings

STEPS TO REPRODUCE
1. Open System Settings and navigate to Network -> Settings -> Proxy
2. Manually configure a Proxy
3. Close System Settings
4. Reopen System Settings -> Network -> Settings -> Proxy

OBSERVED RESULT
Proxy settings are not shown within System Settings.

EXPECTED RESULT
Proxy settings should be shown within System Settings.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.7.12-arch1-1
(available in About System)
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Comment 1 s.moosbauer 2020-08-13 14:08:31 UTC 
Addendum:
STEPS TO REPRODUCE
2. Manually configure a Proxy and apply the settings.


OBSERVED RESULT
Proxy settings are not shown within System Settings. But seem to be configured (tested with Chromium using System Proxy)
Comment 2 laurentlepoittevin 2021-02-10 14:01:28 UTC 
Same things for me.
J'ai également des problèmes de proxy signalé dans le rapport de bug 411316.
Comment 3 laurentlepoittevin 2021-02-10 14:02:53 UTC 
Sorry, in english : I think the problem is related to bug 411316.
I also have proxy problems reported in bug report 411316.
Comment 4 Patrick Silva 2021-06-07 17:34:12 UTC 

*** This bug has been marked as a duplicate of bug 408994 ***