Most probably a driver bug.

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

-- 
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/477830

Title:
  [ASUSTeK Computer INC. 900HA] [Karmic] suspend/resume failure

Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: network-manager

  After a resume from suspend, I am no longer able to connect to a
  wireless network. Network Manager reports "No network devices
  available".  'modprobe ath5k' reports no errors but device is not
  activated. Killing NetworkManager and restarting network also does
  nothing.  Adding SUSPEND_MODULES="ath5k" and/or
  SUSPEND_MODULES="forcedeth" to /etc/pm/config.d/00sleep_module does
  nothing.

  I am using x86 karmic on a EeePC 900HA.

  Attached please find the output of various command pre-suspend and
  post-resume.

  This bug is similar to the following list of bugs all created under
  previous distributions dating back as far as Hardy.  A number of these
  bugs are listed as Solved, but the problem continues under Karmic.

                
  #269630 Network manager: does not remember network after suspend + resume
  #177053 NetworkManager does not successfully reconnect to a wireless network 
after resume from suspend to ram.
  #84313 network-manager not deleting resolvconf information on resume from 
suspend
  #40125 Network cards not detected when resuming from suspend / hibernate
  #31286 Displays repeated keyring dialogs on resume from suspend and login
  #54301 gnome/X freezes upon resume from suspend to RAM
  #209162 dbus seems to crash on resume after suspend taking networkmanager and 
pidgin with it
  #226279 Kernel 2.6.24-17 - broken resume from suspend to RAM
  #226190 [ipw2200] (hardy) On resume from suspend, laptop reports no network 
devices

  
  Occasionally I am able to recover the network connection by running:
  sudo killall NetworkManager; sudo /etc/init.d/NetworkManager start
  but this only seems to work once. If I suspend/resume a second time, I cannot 
recover.

  apt-cache policy network-manager
  network-manager:
    Installed: 0.8~a~git.20091013t193206.679d548-0ubuntu1
    Candidate: 0.8~a~git.20091013t193206.679d548-0ubuntu1
    Version table:
   *** 0.8~a~git.20091013t193206.679d548-0ubuntu1 0
          500 http://ca.archive.ubuntu.com karmic/main Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sat Nov  7 14:16:46 2009
  DistroRelease: Ubuntu 9.10
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.92  metric 
2 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   default via 192.168.1.2 dev wlan1  proto static
  Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
  ProcEnviron:
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: network-manager
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-14-generic i686
  WpaSupplicantLog:
   
  XsessionErrors:
   (gnome-settings-daemon:1892): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:1892): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:1948): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:1940): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/477830/+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