wireless lan does not automatically start when wired connection is dropped
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager-applet (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
kernel 2.6.27-3 x64 8.10
mt-3422 laptop using rtl8180 wifi driver
1. boot up connected to LAN leaving wireless device off.
2. after logged in, unplug LAN wire. connection lost. all good.
3. alt+F2 (turns on wireless device)
network manager does not initialize wifi. no wireless network detected. no network discovery.
4. left click network manager icon. select 'connect to other wireless network' then choose "yournetworkname" from dropped down menu, applet shows info (however, hex key is not being saved by applet (that's another bug)) connect button grayed out.
expected: wireless connection should have been established with preferred wlan after wired LAN was lost.
tried logging off and back in (no LAN and wireless device ON). no results. then tried restarting the computer with no LAN and wireless device ON. success. (however, i also noticed the verbose shutdown stated wlan0 was being deactivated, even thought it acted as if it was off the whole time)
| Michael Rooney (mrooney) wrote | #1 |
| Kyubutsu (jf) wrote | #2 |
| Michael Rooney (mrooney) wrote | #3 |
| Changed in network-manager-applet: | |
| status: | New → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better! This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/