New pptp connections not saved after gutsy upgrade

[Christopher Yee Mon]

Binary package hint: network-manager-pptp

Summary: Before upgrading from Ubuntu Feisty to Gutsy there was a pptp VPN connection installed named VPNConnection. This is on a machine where / and /home are on different partitions. Feisty 32-bit was installed and Gutsy 64-bit was installed on / reformatting the / in the process. After the upgrade, when one attempts to add a pptp VPN Connection, it does not save, unless the name of the new connection is also VPNConnection

Environment:
Upgrade from Feisty 32-bit to Gutsy 64-bit
network-manager-pptp installed on feisty
/ located on one partition and /home located on another

Steps
1. Create a pptp VPN connection named 'VPNConnection' in Feisty
2. Install Gutsy over Feisty with / being reformatted in the process leaving /home as it is. Also mounting the same partition as /home
3. On the new installation, reinstall network-manager-pptp and attempt to create a pptp VPN Connection named something other than 'VPNConnection'
4. Attempt to create a VPN Connection named 'VPNConnection'

Expected Results: After doing the reinstall, the user should be able to successfully create any VPNConnection regardless of whether it's named VPNConnection or not

Actual Results: After the reinstall, when one creates a vpn connection not named VPNConnection, it is not successful. After clicking Add in the VPN Connections dialog box, the wizard is successfully run and each step is gone through successfully. When Apply is clicked though the VPN Connection does not show up in the list in the VPN Connections dialog

When attempting to add the connection that had the previous name 'VPNConnection', it is successful though.

[Christopher Yee Mon (christopher-yeemon)]

The behaviour seems similar to bug 154856 however I could not ascertained since the remarks are not very descriptive. Once VPNConnection was created other pptp connections with different names were successfully created

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.