Well, NM indeed doesn't seem to always come up when dealing with soft
blocks, but Fn-F7 works fine here for stopping and restarting wireless
(but thats a hard block on dell-wifi). I have multiple killswitches
registered: phy0 and dell-wifi for wifi. A soft block for phy0 shows the
device disconnected and not able to bring up interfaces. Soft block for
dell-wireless puts the device in "not ready" state which turns it
unusable until you enable/disable wifi using the applet.
As such, I think it's worth noting this as affecting linux anyway: the
Eeepc's drivers don't properly handle the soft killswitch event: they
really should be causing a hard block, not a soft one (and without
checking, it might be a soft one as a workaround in userland somewhere).
This would need a separate bug, Jeff or Seth, care to open one against
linux for the eeepc drivers?
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- network-manager doesn't reconnect to wireless networks after rfkill blocks
removed
+ network-manager doesn't reconnect to wireless networks after rfkill soft
blocks removed
** Tags added: rfkill soft
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823615
Title:
network-manager doesn't reconnect to wireless networks after rfkill
soft blocks removed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/823615/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
