incorrect vpn status

[Miroslav Zaťko]

old bug #1756720 "nm-applet stop showing vpn status" is back after upgrade to Ubuntu 19.04
---

1. The specific steps or actions you took that caused you to encounter the problem.

      Connect to any VPN. Connection is open.

2. The behavior you expected.

      VPN connection should be displayed as connected in "Settings->Network->VPN" as well as in nm-applet (upper right corner of display)

3. The behavior you actually encountered (in as much detail as possible).

      In "Settings->Network->VPN" it is shown as open but in nm-applet as closed.

---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2018-04-27 (361 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NonfreeKernelModules: nvidia_modeset nvidia
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Tags: disco third-party-packages
Uname: Linux 5.0.0-13-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

[Daniel van Vugt (vanvugt)]

Please also run this command to send us more information about the system:

  apport-collect 1825547

[Miroslav Zaťko (mirec-z)]

apport information

[Miroslav Zaťko (mirec-z)]

apport information

[Miroslav Zaťko (mirec-z)]

apport information

[Miroslav Zaťko (mirec-z)]

apport information

[Sebastien Bacher (seb128)]

Could you take a screenshot showing the issue?

[Miroslav Zaťko (mirec-z)]

Hi there, I am not sure if there was some update in a mean time however now it seems to work correctly.

[Miroslav Zaťko (mirec-z)]

I am not sure how to close this issue correctly so I changed status to "invalid"

[Miroslav Zaťko (mirec-z)]

somehow the situation appeared again, I have no idea what is cause of the status but I was able to make screenshot now

[Sebastien Bacher (seb128)]

The issue looks like similar to https://gitlab.gnome.org/GNOME/gnome-shell/issues/301 which got fixed upstream in 3.30 and in Ubuntu 18.10 and newer. Ideally the fix should be SRUed to the LTS though

[Sebastien Bacher (seb128)]

@Miroslav, what gnome-shell version do you use? The upstream fix has been included in the bionic SRU that got available to updates this week,
https://launchpad.net/ubuntu/+source/gnome-shell/3.28.3+git20190124-0ubuntu18.04.1

Updating to that version should fix the issue, if it doesn't reopen the report

[Miroslav Zaťko (mirec-z)]

GNOME 3.32.1
GNOME Shell 3.32.0

I know about fix for 18.10, I was facing this issue that time already and was happy with the fix.

However right after upgrade to 19.04 the problem was here again but I didn't take screenshot. Then it behave correct for few days and now/today the issue is back again so I added screenshot. Unfortunately I am not able to identify anything more about the issue