network-manager 1.2.6 won't connect to vpn and displays false connected message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages.
The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated.
---
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-03-19 (10 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Package: network-manager 1.2.2-0ubuntu0.
PackageArchitec
Tags: xenial
Uname: Linux 4.9.16 x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
no longer affects: | linux (Ubuntu) |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1677175
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.