Network starts disabled without apparent reason

Bug #541488 reported by Jakub Witkowski on 2010-03-18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)

Bug Description

Binary package hint: network-manager

Once in about thee bootups, network-manager starts in disabled state for no apparent reason. When switched on, it normally finds wifi networks and connects without a problem.

Release: Lucid (up-to-date as of March 18)
Version: 0.8-0ubuntu2
Hardware: HP TC1100 tablet PC
Network adapters:
02:07.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
03:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)

Atheros card is actually a PC-Card kept inserted all the time (it certainly was present during bootups in question).

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Mar 18 21:13:10 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100315)
InterestingModules: b44
IpRoute: dev wlan0 proto kernel scope link src metric 2 dev wlan0 scope link metric 1000
 default via dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
Package: network-manager 0.8-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: network-manager
Uname: Linux 2.6.32-16-generic i686

The same has just happened to me on a desktop at work, when I resumed it from hibernation.
This desktop has no wifi but instead two Ethernet interfaces connected to two different networks.

It is possible that it also was caused by hibernation on my tablet as well, in some roundabout way, since the last time it happened, it was during a supposedly clean boot after a failed attempt to resume.

This appears to be closely related to sleep and hibernation - does Network-Manager save it's disabled state to disk anywhere?

I had two more cases of n-m launching in disabled state, one on a laptop brought up after a broken sleep (battery ran out) and one on a desktop that did not hibernate properly.

zorblek (zorblek) wrote :

This looks like it might be related to bug #291062.

This appears to be related to failed sleep/hibernate (if not, then it seems like it would be 291062, which should have been fixed long ago).

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at . Thanks again and we appreciate your help.

Changed in network-manager (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
tags: added: nm-wrong-enabled-state
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers