Recent Changes have broken VPNC via Network Manager

Bug #1286654 reported by Lonnie Lee Best
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
New
Undecided
Unassigned
VPNC
New
Undecided
Unassigned
network-manager-vpnc (Ubuntu)
New
Undecided
Unassigned
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Since Friday 2-28-2014, Ubutnu 14.04 has seemingly made changes to the way the Network Manager establishes a VPNC connection to a cisco firewall.

Normally, you establish a VPNC connection with these steps (assuming you've already configured the VPNC connection):
1) Click on the Network Connection manager's indicator.
2) Select "VPN Connections"
3) Select the VPNC connection's name you've previously configured.

The normal procedure requires no further steps; you typically see a system notification soon after this informing you that your VPN connection is now established, and then that notification fades away without explicit effort.

Now, instead, (after step 3) a dialog pops up (unnecessarily) which has two buttons "Connect" and "Cancel". If you click the "connect" button it cancels! If you click the "cancel" button it connects!

I'm not proposing that this dialog be fixed, I'm proposing that it be removed (as it was before). It is completely unnecessary; the user has already been burdened with 3 steps that clearly indicate their intention is to connect to the VPN. Why then prompt them again, asking them if they want to connect?

This silly dialog is specific to VPNC connections. When I use the network manager to vpn via OpenVPN, this unnecessary dialog doesn't appear.

Tags: trusty
description: updated
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

I'm not experiencing this bug today.

You know, around the time I experienced this bug, I had recently installed these packages:
sudo apt-get install lxde xfdesktop4

Later I removed them:
sudo apt-get remove lxde xfdesktop4

Perhaps that is what caused and fixed this issue?

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

FYI: This bug came back again tonight.

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

Can anyone else confirm this?

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

Today, I'm not experiencing this bug. I will report back if it comes back again.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.