[Bug 1299282] [NEW] need to restart network-manager after resume from suspend
Launchpad Bug Tracker
1299282 at bugs.launchpad.net
Tue Apr 8 22:37:49 UTC 2014
You have been subscribed to a public bug:
possibly related to bug #1289884 , but when i resume from suspend none
of my interfaces (wireless, wired usb, bluetooth connection) are
visibile to network-manager until i restart it.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 28 15:56:30 2014
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2014-02-24 (32 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
IpRoute:
default via 10.9.0.1 dev eth0 proto static
10.9.0.0/24 dev eth0 proto kernel scope link src 10.9.0.38 metric 1
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=false
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
B0:79:94:D7:0E:0E bluetooth disconnected /org/freedesktop/NetworkManager/Devices/2
wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.8 connected enabled enabled disabled enabled disabled
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug gnome3-ppa third-party-packages trusty
--
need to restart network-manager after resume from suspend
https://bugs.launchpad.net/bugs/1299282
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to systemd in Ubuntu.
More information about the foundations-bugs
mailing list