Are you still seeing this? If so, are you still using 10.04?

That's an old issue in 10.04; which was fixed in newer releases.

10.04 shares the "Sleep" function with things like "Disable wireless",
which leads to confusion. When this happens you may want to try toggling
"Disable wireless" or "Disable networking" in nm-applet context menu.

Since this is fixed in later releases, I'll close this bug as Fix
Released. Please let us know if backporting the fix to 10.04 should be
considered.

** Changed in: network-manager (Ubuntu)
       Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/886991

Title:
  Wi-Fi Does not resume after laptop sleep -- Intel PRO/Wireless iwlagn

Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  This has happened a couple of times recently.  I sleep my Lenovo T61p
  laptop by closing the lid.  When I reopen it the WiFi does not re-
  enable.  The bluetooth light is on but not the wifi light.  I tried to
  reenable the Wifi by sliding the radio switch off and back on but it
  didn't help.  The following lines from daemon.log may be relevant:

  
  Nov  6 19:21:59 sancho NetworkManager: <info>  WiFi now disabled by radio 
killswitch
  Nov  6 19:21:59 sancho NetworkManager: <info>  (wlan0): bringing up device.
  Nov  6 19:22:00 sancho bluetoothd[16750]: HCI dev 0 registered
  Nov  6 19:22:00 sancho bluetoothd[16750]: HCI dev 0 up
  Nov  6 19:22:00 sancho bluetoothd[16750]: Starting security manager 0
  Nov  6 19:22:00 sancho bluetoothd[16750]: Adapter /org/bluez/16736/hci0 has 
been enabled
  Nov  6 19:22:00 sancho bluetoothd[16750]: Stopping security manager 0
  Nov  6 19:22:00 sancho bluetoothd[16750]: HCI dev 0 down
  Nov  6 19:22:00 sancho bluetoothd[16750]: Adapter /org/bluez/16736/hci0 has 
been disabled
  Nov  6 19:22:03 sancho NetworkManager: bluez_manager_bdaddr_added_cb: BT 
device Stephen’s iPhone (64:B9:E8:A2:29:9A) added (NAP)
  Nov  6 19:22:03 sancho NetworkManager: <info>  (64:B9:E8:A2:29:9A): new 
Bluetooth device (driver: 'bluez')
  Nov  6 19:22:03 sancho NetworkManager: <info>  (64:B9:E8:A2:29:9A): exported 
as /org/freedesktop/NetworkManager/Devices/16
  Nov  6 19:22:03 sancho NetworkManager: <info>  (64:B9:E8:A2:29:9A): now 
managed
  Nov  6 19:22:03 sancho NetworkManager: <info>  (64:B9:E8:A2:29:9A): device 
state change: 1 -> 2 (reason 2)
  Nov  6 19:22:03 sancho NetworkManager: <info>  (64:B9:E8:A2:29:9A): 
deactivating device (reason: 2).
  Nov  6 19:22:03 sancho NetworkManager: <info>  (64:B9:E8:A2:29:9A): device 
state change: 2 -> 3 (reason 0)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: network-manager 0.8-0ubuntu3.2
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Nov  6 19:53:35 2011
  ExecutablePath: /usr/sbin/NetworkManager
  Gconf:
   
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  IpRoute:
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.104  metric 
1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   default via 192.168.1.1 dev eth0  proto static
  Keyfiles: Error: [Errno 2] No such file or directory
  ProcEnviron: PATH=(custom, no user)
  SourcePackage: network-manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/886991/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to