Bug 326974

Summary: Connection manager doesn't store password for PPTP connection
Product: [Plasma] plasma-nm Reporter: Adrian Piotrowicz <nexces>
Component: editorAssignee: Lukáš Tinkl <lukas>
Status: RESOLVED FIXED    
Severity: normal CC: jgrulich, renszarv07
Priority: NOR    
Version: 0.9.3.0   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 0.9.3.2
Sentry Crash Report:

Description Adrian Piotrowicz 2013-11-01 05:50:40 UTC 
VPN (pptp) connection editor offers option to store password for a connection, however it doesn't work.
Regardless of this option I'm always asked to provide password whenever I'm trying to connect.

Reproducible: Always

Steps to Reproduce:
1. Create a PPTP connection inside the Network Management Settings window
2. Select "Store" in the "VPN (pptp)" tab and provide password
3. Select this connection from the main network manager widget 
Actual Results:  
Password prompt

Expected Results:  
Connection should be established without asking for password.

It seems that there is no password stored in KWallet for VPN connection.

Also password field is disabled and empty when opening connection settings dialog again after saving connection settings.
Comment 1 Jan Grulich 2013-11-01 08:51:48 UTC 
Do you use the new networkmanagement applet or the old one? Does your VPN connection contain manual IPv4 addreses?
Comment 2 Adrian Piotrowicz 2013-11-02 05:49:21 UTC 
This is new network management applet (version 0.9.3.0).
I'm using KDE 4.11.2.
As for IPv4 addresses, I'm not configuring anything by hand, everything is being setup automatically.
Comment 3 Jan Grulich 2013-11-02 16:29:04 UTC 
Git commit b2e9be54e2556ac84c61115bf62ed83c5a3e69e0 by Jan Grulich.
Committed on 02/11/2013 at 16:28.
Pushed by grulich into branch 'master'.

Password input should be enabled, because the default value is store

M  +1    -1    vpn/pptp/pptpprop.ui

http://commits.kde.org/plasma-nm/b2e9be54e2556ac84c61115bf62ed83c5a3e69e0
Comment 4 Jan Grulich 2013-11-02 16:31:18 UTC 
Your problem should be fixed by this bug https://bugs.kde.org/show_bug.cgi?id=326632.