OpenVPN unrecoverably unavailable after sleep

[Rüdiger Kupper]

Just what the title says.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.3
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 4 17:15:03 2015
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (905 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 192.168.179.1 dev wlan0 proto static metric 400
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.179.0/24 dev wlan0 proto kernel scope link metric 400
JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2015-04-24 (163 days ago)
WifiSyslog:

nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Turmbraeu Gastzugang_5GEXT 3e637552-b358-4ff8-8b36-8e8c9dc1e239 /org/freedesktop/NetworkManager/ActiveConnection/0
 ttyACM1 gsm disconnected /org/freedesktop/NetworkManager/Devices/3 -- -- --
 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

[Rüdiger Kupper (ruediger.kupper)]

Steps to reproduce:
- Connect to OpenVPN via Network manager.
- Put your computer to sleep and wake it up again.
- Observe that OpenVPN connection is not automatically reestablished.
- Observe that manually reestablishing OpenVPN fails.
- Observe that restarting ModemManager or NetworkManager service does not help.
- Observe that rebooting is the only way of recoverng from this state.