network-manager starts up with wireless disabled

[ԜаӀtеr Ⅼарсһуnѕkі]

Lubuntu 11.10
network-manager 0.9.1.90-0ubuntu5

As I have wireless connections already setup-- ones that connect automatically and are available to all users-- I would expect these connections to, well, connect automatically upon startup. Just like the ethernet ones do!

Instead, nm-applet appears greyed out. Right clicking on the icon finds wireless, as with all the other connections (though, admittedly, there are no relevant connections set up), unchecked. If I, then, click on wireless, my connection automatically starts up. Therefore, the problem seems to be not in the connection, but in the fact that the wireless is disabled.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Nov 18 23:24:59 2011
EcryptfsInUse: Yes
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IpRoute:
 default via 192.168.1.1 dev wlan0 proto static
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.114 metric 2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
 WimaxEnabled=true
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

This should NOT be the same bug as:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/886916?comments=all
at least as far as I can tell. With that bug, you can still get online with no other steps. With this bug, it is necessary to actually click on "Enable Wireless." Still a problem with 0.9.1.90-0ubuntu5.1 though it is more likely to happen if the power is disconnected.

[Mathieu Trudel-Lapierre (cyphermox)]

How are you shutting down your computer? Are you actually shutting down or just suspending (or using hibernate)?

This seems to me like it's a bug that should have been fixed long ago, and since rfkill state shouldn't affect the "Wireless enabled" menu, I'm at a loss as to explain it.

Please attach the output of the 'rfkill list' command immediately after starting up, before changing anything on your computer.

Thanks in advance!

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

To have the problem, I need to cleanly shutdown and remove the power.
Then I have:
$ rfkill list
0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

If I shutdown cleanly and cold boot, restart, or resume from suspend
(sorry, never had any luck with hibernating doing anything other than
being a shutdown equivalent, but that's another story…), then I have:
$ rfkill list
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

seems fixed in precise.

On 03/22/2012 09:18 PM, Launchpad Bug Tracker wrote:
> [Expired for network-manager (Ubuntu) because there has been no activity
> for 60 days.]
>
> ** Changed in: network-manager (Ubuntu)
> Status: Incomplete => Expired
>