Disabling wireless connection should trigger rfkill
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Manager Applet |
Unknown
|
Medium
|
|||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
network-manager-applet (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
When disabling wireless networking in the network manager applet, the rfkill switch for the wireless card should be triggered.
For two reasons:
1) No sense drawing power for the transmitter if the user does not want to use wireless.
2) On some systems (eg. EeePC) there is no hw switch, so disabling the wireless connectivity should kill all wireless activity.
Furthermore due to 2) all wireless drivers should initialize with rfkill enabled and wait for NM to enable wireless communications. Otherwise booting a device without a hw switch on a plane could cause problems. (So this affects NM and the kernel as well). Perhaps this should be a configuration option: default to on, default to off, default to last status.
Thanks,
Dominik
Changed in network-manager-applet (Ubuntu): | |
status: | New → Confirmed |
Changed in network-manager-applet (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in network-manager-applet: | |
status: | Unknown → New |
Changed in network-manager-applet: | |
importance: | Unknown → Medium |
status: | New → Unknown |
If I boot and X.org fails to start I want network access in text mode so I can apt-get a new version of my X.org driver etc. Also being able to boot without network access for airplanes is also a nice feature but there should be a way to do both I think.