getting the ball rolling for lucid SRU (that's a pretty hefty patch at 26KB!)
** Patch added: "debdiff for lucid" https://bugs.launchpad.net/ubuntu/lucid/+source/network-manager/+bug/524454/+attachment/2494956/+files/lp524454-lucid.debdiff -- 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/524454 Title: Networking is disabled on boot (usually after suspend/hibernate) Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Lucid: Confirmed Status in “network-manager” source package in Maverick: Fix Released Status in “network-manager” package in Debian: Fix Released Bug description: 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 a resume from suspend/hibernate. Right-clicking on the Network Manager applet and choosing "Enable Networking" solves the problem. 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 second 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 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. This bug is a regression in the new NM 0.8. The upstream has fixed this bug and 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 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/524454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
