#4267 HIGH Not Tri: networks all appear twice in mesh view

[Zarro Boogs per Child]

#4267: networks all appear twice in mesh view
------------------------+---------------------------------------------------
   Reporter:  sj        |       Owner:  marco        
       Type:  defect    |      Status:  new          
   Priority:  high      |   Milestone:  Not Triaged  
  Component:  sugar     |     Version:               
 Resolution:            |    Keywords:  blocks?:8.2.0
Next_action:  diagnose  |    Verified:  0            
  Blockedby:            |    Blocking:               
------------------------+---------------------------------------------------

Comment(by mtd):

 Replying to [comment:14 wad]:
 > The requested logs are attached.  I'm very curious why you can't
 reproduce the results.  Many people have seen this --- few people report
 not seeing the problem.

 Thanks for the logs - I didn't really expect you to have time.
 Unfortunately I won't be able to look at this for another 8-10 hours.

 This part of shell.log appears quite suspicious:

 {{{
 [martin at cree sugar]$ grep Net\( shell.log
 1219901685.537315 DEBUG root: Net(Watlington): caps 0x10000001
 1219901685.766525 DEBUG root: Net(pinewood): caps 0x1
 1219901685.861184 DEBUG root: Net(Watlington): caps 0x10000001
 }}}

 Each of those lines is going to cause a circle to appear in the mesh view.
 That output's from /usr/share/shell/sugar/hardware/nmclient.py:142 (or
 thereabouts; line number from current git), and the lack of "appeared" in
 the shell.log makes me suspect that we're seeing two "Watlington"s when we
 call getProperties() on the NM network device.  So now I'd really be
 interested to see the output of:

 {{{
 dbus-send --system --print-reply --reply-timeout=2000 type=method_call
 --dest=org.freedesktop.NetworkManager
 /org/freedesktop/NetworkManager/Devices/eth0
 org.freedesktop.NetworkManager.getProperties
 }}}

 I can't reproduce the problem because I don't have any hidden access
 points.  That's left out of your test case description because you
 probably thought it would be so obvious that nobody would ever think of
 doing the tests without that situation after reading all through this bug.

 When I get home later I will make my AP hidden and try it out again,
 including investigating the dbus-send output I mentioned.

 Martin

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