Bug 413583

Summary: vpnc passwords are not stored in KWallet
Product: [Applications] systemsettings Reporter: madcatx
Component: kcm_networkmanagementAssignee: Jan Grulich <jgrulich>
Status: RESOLVED FIXED    
Severity: normal CC: jgrulich, kde, kiwimisc
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description madcatx 2019-10-29 09:20:02 UTC 
I was having some issues with my VPN (Cisco vpnc) connection so I ended up deleting it in SystemSettings and recreating it again with proper settings. Ever since then the group password and user password are not stored in KWallet and NM prompts me to enter them every time I want to connect. There is no entry for the created VPN connection in KWallet. After a few updates and attempts to delete the connection and create it again the problem remains. Other VPN connection settings are stored just fine and so are passwords for WiFi networks etc.

What can I do to trace the cause of the problem?
Comment 1 Jan Grulich 2019-10-29 09:21:52 UTC 
I think there was a bug in NetworkManager causing this, see [1]. What is your NetworkManager version?

[1] - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230
Comment 2 madcatx 2019-10-29 09:47:37 UTC 
(In reply to Jan Grulich from comment #1)
> I think there was a bug in NetworkManager causing this, see [1]. What is
> your NetworkManager version?
> 
> [1] - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230

This looks likely, my NM is 1.20.4. It looks like the fix didn't make it into 1.20.4.
Comment 3 madcatx 2019-11-04 17:45:57 UTC 
Confirmed, application of

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/43b7e669482822edec3dbf1d410825eb4ce02abe

to NM fixes the issue.
Comment 4 Jan Grulich 2019-11-29 11:57:22 UTC 
*** Bug 414280 has been marked as a duplicate of this bug. ***
Comment 5 Jan Grulich 2019-12-05 10:58:25 UTC 
*** Bug 411512 has been marked as a duplicate of this bug. ***