After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 696431 - Network indicator displays nonfunctional on/off VPN toggle when multiple VPN connections are configured
Network indicator displays nonfunctional on/off VPN toggle when multiple VPN ...
Status: RESOLVED DUPLICATE of bug 682929
Product: gnome-shell
Classification: Core
Component: network-indicator
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-03-23 01:42 UTC by Michael Catanzaro
Modified: 2013-03-23 12:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Catanzaro 2013-03-23 01:42:39 UTC 
I used the Network panel in gnome control center to configure two VPN interfaces.  Now the gnome shell network indicator displays three types of connections: wired, wireless, and VPN, each with an on/off toggle. The wired and wireless toggles always work as expected. When I have an active VPN connection, the VPN toggle works as expected and closes the VPN connection. But if I do not have an active VPN connection, the toggle is nonfunctional: clicking on it does nothing. This is somewhat sensible, since the toggle has no way of picking between either of my two possible connections. But the toggle should not be displayed at all if it's not going to work.

Perhaps it'd be more sensible to have on/off toggles next to each individual VPN connection.
Comment 1 Giovanni Campagna 2013-03-23 12:51:34 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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