#4074 HIGH 8.2.0 (: When connecting to access point, mesh still blinks on different channel

Zarro Boogs per Child bugtracker at laptop.org
Mon Sep 29 04:29:01 EDT 2008


#4074: When connecting to access point, mesh still blinks on different channel
-------------------------------+--------------------------------------------
   Reporter:  bert             |       Owner:  dcbw                
       Type:  defect           |      Status:  reopened            
   Priority:  high             |   Milestone:  8.2.0 (was Update.2)
  Component:  network manager  |     Version:                      
 Resolution:                   |    Keywords:                      
Next_action:  design           |    Verified:  0                   
  Blockedby:                   |    Blocking:                      
-------------------------------+--------------------------------------------
Changes (by mtd):

 * cc: mtd (added)
  * status:  closed => reopened
  * next_action:  finalize => design
  * resolution:  fixed =>


Comment:

 I don't think this was ever fixed, and I am not sure it's a Sugar issue.
 Attached is shell.log from joyride-2974 demonstrating that NetworkManager
 never sends "DeviceNoLongerActive" for msh0 if it's activating and there
 is a user switch to another device.

 I've attached my shell.log, and shell.log trimmed down so you can see this
 sequence of events:

 0. Normal stuff

 1. Click on "Mesh Device 1" in Sugar --> DeviceNoLongerActive for msh0,
 DeviceActivating for msh0

 2. Click on "OBS6" in Sugar --> DeviceActivating for eth0, *nothing* for
 msh0

 I've also attached the kludge that avoids the issue if the mesh was
 clicked first, but otherwise we're stuck assuming only one device is
 active at any time and disabling everything else when another starts
 activating (perhaps we should just stop anything that's activating (not
 active)).

 I don't think this is worth doing much more than kludging until we get NM
 0.7 in, but I figured this is the earliest bug of this nature and doesn't
 seem to have been fixed, it seems a fitting tracker bug.

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


More information about the Bugs mailing list