NM indicator unable to re-enable wireless after disabling it

Bug #1017051 reported by Brian
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
NetworkManager
Fix Released
Medium
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

With network-manager 0.9.4.0 and network-manager-gnome 0.9.4.1, if I disable wireless by right-clicking on the applet and unchecking "Enable Wireless", then the menu item is greyed out and cannot be re-enabled.

It appears that when disabling, the rfkill soft block is set on the wireless device. NM then reports the device as hardware disabled (when in fact it is only soft-disabled), causing the menu item to be disabled.

If one manually removes the soft block using `rfkill unblock <ID>`, then it is possible to re-enable wireless from the applet.

The applet should instead show enable the menu option when the device is only soft-blocked, and remove the soft block when the enable option is selected.

Tags: precise
Revision history for this message
Thomas Hood (jdthood) wrote :

Same as bug #823615?

Revision history for this message
Brian (rephorm) wrote :

It could be related, but its not the same issue. #823615 is about NM not recognizing when the soft block is removed. This is not the case on my system. Removing the soft block (using `rfkill`) allows me to re-enable wifi through NM.

Revision history for this message
Brian (rephorm) wrote :
Thomas Hood (jdthood)
summary: - Unable to re-enable wireless after disabling via nm-applet
+ nm-applet unable to re-enable wireless after disabling it
summary: - nm-applet unable to re-enable wireless after disabling it
+ NM indicator unable to re-enable wireless after disabling it
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Thomas Hood (jdthood) wrote :

Also similar, bug #583308.

Revision history for this message
Brian (rephorm) wrote :

It looks like this specific issue could be unique to sony laptops. As mentioned in the upstream bug report, there are two radio killswitches. When the one that corresponds to the physical switch on the laptop is soft blocked, the bios hard blocks the second killswitch, causing NM to think that it can't unblock. There is a proposed workaround in the upstream report.

Revision history for this message
Thomas Hood (jdthood) wrote :

#497623 mentions Toshiba and Dell laptops. But that could be another underlying issue, of course.

Thomas Hood (jdthood)
tags: added: precise
Changed in network-manager:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in network-manager:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.