#10532 NORM 10.1.3: Users disable networking in nm-applet, and Sugar does not re-enable it

[Zarro Boogs per Child]

#10532: Users disable networking in nm-applet, and Sugar does not re-enable it
-------------------------------------+--------------------------------------
           Reporter:  godiard        |       Owner:  godiard      
               Type:  defect         |      Status:  new          
           Priority:  normal         |   Milestone:  10.1.3       
          Component:  gnome-desktop  |     Version:  not specified
         Resolution:                 |    Keywords:               
        Next_action:  never set      |    Verified:  0            
Deployment_affected:                 |   Blockedby:               
           Blocking:  10409          |  
-------------------------------------+--------------------------------------
Changes (by martin.langhoff):

 * cc: martin.langhoff (added)
  * owner:  martin.langhoff => godiard


Comment:

 Patch to sugar's cpsection/network/model.py attached.

 With this patch, we

  * Consider nm wireless and rfkill state to populate the checkbox.
  * When enabling and disabling we perform the equivalent actions to what
 nm-applet does if you enable/disable both 'networking' and 'wireless
 networking'.

 Discussion - NM dbus API: The dbus api documentation is inaccurate. It
 talks about the Sleep(bool) method call; but nm-applet uses Enable(bool).
 This is true both on NM0.7 (F11) and NM0.8 (F14). So this patch uses
 Enable() to match nm-applet.

 Discussion - rfkill: when we bring the network down, we are still applying
 rfkill. This confounds the GNOME side as nm-applet + NM will not report
 the wlan card if it's rfkilled. I am devising a workaround, but I wonder
 why we rfkill.

-- 
Ticket URL: <http://dev.laptop.org/ticket/10532#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system