network-manager doesn't recognize wlan0 under specific conditions

Asked by Trevor Norris on 2011-02-15

I wanted to ask this question here before posting it as a potential bug. The problem is that network manager isn't detecting my wireless card, but it can be manually started and used to connect to a wireless network. Here are the steps to reproduce the problem:
- start computer with wireless network disabled, ethernet enabled and plugged in.
- after boot and login, lock computer.
- unplug ethernet cable.
- unlock computer and try to connect to wireless network.

nm-tool gives the following data:
Type: 802.11 WiFi
Driver: iwlagn
State: unavailable
Default: no
HW Address: XX:XX:XX:XX:XX:XX

Though running the following commands allows me to successfully connect to an available wireless network:
$ ifconfig wlan0 up
$ iwconfig wlan0 essid GUESTWLAN
$ dhclient

Even after successfully connecting to a wireless network, and browsing the web (doing it now) the Network Manager still doesn't recognize the wireless has been activated. Also, strangely nothing happens if I hit the button to enable the wireless network. The following message pops up in kern.log:
- iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio.

But still nothing happens. Is there something I'm missing, or is this a bug with the Network Manager?

I've collected all the log files, and will provide them if needed. Here's my computers info:
Linux 2.6.35-26-generic #46-Ubuntu SMP Sun Jan 30 06:59:07 UTC 2011 x86_64 GNU/Linux
Ubuntu 10.10
network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
network-manager-gnome 0.8.1+git.20100809t190028.290dc70-0ubuntu3
*-network
     description: Wireless interface
     product: Centrino Advanced-N 6200
     vendor: Intel Corporation

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu network-manager Edit question
Assignee:
No assignee Edit question
Last query:
2011-02-15
Last reply:
2011-02-18

Yes, this appears to be a bug. I recommend reading https://help.ubuntu.com/community/ReportingBugs carefully, search to see if the bug has already been reported (that page explains how), then reproduce the problem, invoke ubuntu-bug with the PID of the NetworkManager process (if that doesn't make sense, it probably will once you've finished reading https://help.ubuntu.com/community/ReportingBugs), and file a bug report. Relevant log files can be attached to the bug report.

Then you can link this question and your bug to each other with the "Link existing bug" link on this question page. While it is a good idea to do that, your bug report should be self-contained--it should not be necessary for the Ubuntu developers to refer to this question, in order to understand and appreciate your bug report.

(I *think* network-manager is the right package to report this bug against. But if not, that can, and will, be easily changed after the bug report is submitted.)

Trevor Norris (trev-norris) said : #2

Thanks for the information. I'll take the necessary steps.

Can you help with this problem?

Provide an answer of your own, or ask Trevor Norris for more information if necessary.

To post a message you must log in.