This bug was fixed in the package gnome-shell - 3.28.3-0ubuntu0.18.04.2
---------------
gnome-shell (3.28.3-0ubuntu0.18.04.2) bionic; urgency=medium
* New upstream release (LP: #1718931, LP: #1782614)
*
debian/patches/30-remoteMenu-Prevent-the-shell-from-becoming-unrespons.patch,
debian/patches/magnifier.js-Fix-zoom-juddering.patch,
debian/patches/st-label-Unset-clutter-text-instance-on-disposal.patch,
debian/patches/st-texture-cache-Don-t-add-NULL-textures-to-cache.patch,
debian/patches/st-texture-cache-Save-cairo-surfaces-to-a-different-map.patch,
debian/patches/ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch:
- Drop patches applied on the 3.28 branch
* debian/patches/js-fix-invalid-access-errors.patch:
- Refreshed to reflect upstream changes
* d/p/popupMenu-Don-t-handle-key-presses-directly-if-there-are-.patch
- Don't handle key presses directly if there are modifiers (LP: #1784671)
* debian/patches/workspace-fix-repositioned-windows-in-activities.patch:
- Cherry-pick from upstream 3.28 branch
-- Marco Trevisan (Treviño) <ma...@ubuntu.com> Fri, 03 Aug 2018
07:18:24 +0100
** Changed in: gnome-shell (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1718931
Title:
No VPN autoconnect
Status in NetworkManager:
Incomplete
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Bionic:
Fix Released
Bug description:
[ Impact ]
When setting up VPN to auto connect with wifi (done through nm-
connection-editor) the wifi never manages to connect. However if I
unselect the auto connect option while it is attempting a reconnection
then it manages to connect to both (wifi and VPN). Doing the
connection manually also poses no issues
[ QA ]
This is part of the upstream fix:
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
ProblemType: BugDistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 22 13:15:55 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-09-09 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
IpRoute:
default via 192.168.0.1 dev wlp6s0 proto static metric 600
169.254.0.0/16 dev wlp6s0 scope link metric 1000
192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=trueSourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
wlp6s0 wifi connected /org/freedesktop/NetworkManager/Devices/2
VM5055940 85b8f881-7ed9-477a-9c39-9afb5a40bda9
/org/freedesktop/NetworkManager/ActiveConnection/1
lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 --
-- --
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.8.2 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1718931/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
