registry team mailing list archive

[papukaija <524454@xxxxxxxxxxxxxxxxxx>]

This bug is affecting 60 people which are probably all Lucid users.

** Description changed:

  Binary package hint: network-manager
  
  My networking is disabled every time I boot. To correct, I must right-
  click on Network Manager applet and choose "Enable Networking," after
  which my wireless networks become available and I can get online.
  
  I'm using Lucid on a MacBookPro2,1
  
  ------SRU details----
  Impact: This bug keeps the the networking disabled after suspend/resume. Right-clicking on the Network Manager applet and choosing "Enable Networking" solves the problem.
  
- How the bug has been addressed: The upstream has provided two patches
- (both are attached to this bug). There are two patches because the
- person who did the fix forgot something from the first commit and
- therefore made a socond commit. The links to commits and patches can be
- found at comments 59 and 61.
+ How the bug has been addressed: NM 0.8 has some bugs witch are partially
+ listed at http://live.gnome.org/NetworkManager/ReleaseProcess The
+ upstream has provided two patches (both are attached to this bug). There
+ are two patches because the person who did the fix forgot something from
+ the first commit and therefore made a socond commit. The links to
+ commits and patches can be found at comments 59 and 61. Some of these
+ bugs including this bug are fixed in NM 0.8.1
  
  TEST CASE:
- Suspend or resume. On resume you should not have a working network.
+ Suspend or hibernate. The upstream report isn't very detailed about this, but in my case that process is unsuccessful. On resume you should not have a working network.
+ 
  To solve:
   1) run
  service network-manager stop
  rm /var/lib/NetworkManager/NetworkManager.state
  service network-manager start
  
  or 2) right-click on Network Manager applet and choose "Enable
  Networking,"
  
  or 3) Reboot.
  
- Regression potential: Really none. Two simple patches shouldn't be the
- end of the world.
- 
+ Regression potential: Really none. This bug is a regression in the new
+ NM 0.8. The upstream has fixed this bug ans some other bugs in NM 0.8.1.
  
  ------------------------
  ProblemType: Bug
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory
  Date: Fri Feb 19 14:25:27 2010
  DistroRelease: Ubuntu 10.04
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  IpRoute:
   10.45.43.0/24 dev wlan0  proto kernel  scope link  src 10.45.43.23  metric 2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   default via 10.45.43.1 dev wlan0  proto static
  Keyfiles: Error: [Errno 2] No such file or directory
  Package: network-manager 0.8~rc2-0ubuntu1
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
  SourcePackage: network-manager
  Uname: Linux 2.6.32-13-generic i686

** Changed in: network-manager (Ubuntu Lucid)
       Status: New => Confirmed

** Tags added: maverick

-- 
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.