Bug 1319488

Summary: [network] openvpn padlock icon does not reflect connection state
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: blueowl, choeger, dcbw, fmuellner, huzaifas, lkundrak, otaylor, steve, thaller
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 14:00:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joachim Frieben 2016-03-20 15:52:53 UTC
Description of problem:
When using a VPN connection in current Fedora 24, then the (GNOME shell) panel icon of the underlying wired connection is replaced by a padlock icon which symbolizes the secure VPN connection. In the case of a non-VPN wired connection, loss of connectivity is displayed by a different icon with a question mark. It seems that no such alternate icon is provided and/or handled by NetworkManager-openvpn; this implies that changes of the connection state remain hidden when using a VPN connection.

Version-Release number of selected component (if applicable):
NetworkManager-openvpn-1.2.0-0.3.beta2.fc24

How reproducible:
Always

Steps to Reproduce:
1. Start VPN connection.
2. Inhibit network connectivity.

Actual results:
Icon of VPN connection remains unaltered.

Expected results:
Icon of VPN connection reflects state of connectivity.

Additional info:
When connectivity is lost, then NetworkManager-openvpn should replace the padlock symbol by a modified padlock symbol which notifies the user unambiguously, e.g. by adding a question mark similar to the case of an ordinary wired connection.

Comment 1 Blueowl 2016-08-09 19:44:04 UTC
What icon do you see? What icon would you expect?

What is the status of NM connections?
$ nmcli general
$ nmcli device

Comment 2 Joachim Frieben 2016-08-10 03:41:56 UTC
After disconnecting my cable modem from upstream, (global) network connectivity gets lost but the network connection is still symbolized by the normal padlock icon (network-vpn-symbolic). No indication of the loss of connectivity is given.
Only after turning off the VPN connection, the padlock icon is replaced by some wired-network icon (network-wired-no-route-symbolic) which unambiguously indicates the loss of connectivity. I would expect that during an active VPN connection, loss of connectivity is symbolized by a similar icon (network-vpn-no-route-symbolic) which, however, does not exist yet.

The status of the NetworkManager connections after loss of connectivity becomes:

$ nmcli general
STATE                  CONNECTIVITY  WIFI-HW  WIFI      WWAN-HW  WWAN
connected (site only)  limited       enabled  disabled  enabled  enabled

$ nmcli device
DEVICE   TYPE      STATE        CONNECTION
enp0s25  ethernet  connected    enp0s25
tun0     tun       connected    tun0
wlp3s0   wifi      unavailable  --
lo       loopback  unmanaged    --

Comment 3 Fedora End Of Life 2017-07-25 20:22:12 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-08-08 14:00:11 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.