Seth Forshee, good news, bluntly restarting NetworkManager allowed me to
continue without the reboot:
$ sudo service network-manager restart
[sudo] password for sarnold:
network-manager stop/waiting
network-manager start/running, process 6165
I didn't see anything in my logs that suggests what
From what I see in the logs there's not even an attempt to establish a
connection after resume, so I think the problem is likely with network-
manager. Reassigning.
** Package changed: linux (Ubuntu) = network-manager (Ubuntu)
--
You received this bug notification because you are a member of
I've seen some reports about NetworkManager failing to work after
suspend, and since none of your connections work I'd guess this is what
you're seeing. Next time this happens see if restarting NetworkManager
fixes the problem.
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1251054
Title:
networking didn't return from suspend
Status in “linux”
** Description changed:
Wireless networking did not work when I resumed from suspend.
Using the indicator/applet to Enable Networking didn't associate my
wireless with the AP. Plugging in an Ethernet cable did not bring back
- networking.
+ networking. The hardware rfkill switch did not
5 matches
Mail list logo
