#8603 NORM Not Tri: weirdnesses in wlan networking user interface (in Neighborhood and in lower frame)

[Zarro Boogs per Child]

#8603: weirdnesses in wlan networking user interface (in Neighborhood and in lower
frame)
-----------------------------+----------------------------------------------
 Reporter:  thomaswamm       |         Owner:  dcbw                             
     Type:  defect           |        Status:  new                              
 Priority:  normal           |     Milestone:  Not Triaged                      
Component:  network manager  |       Version:  Development build as of this date
 Keywords:                   |   Next_action:  reproduce                        
 Verified:  0                |     Blockedby:  6995                             
 Blocking:                   |  
-----------------------------+----------------------------------------------
 I have seen some weirdnesses in the networking user interface in beta
 build 8.2-760.  These might be side-effects of unfinished work-in-progress
 related to #6995 or other wlan tickets.  So this new ticket might be just
 a reminder.  It might also relieve other testers of the chore of filing a
 ticket, if they see similar weirdnesses.  I consider these low priority.

 Weirdness !#1:  Sometimes in the frame I have seen '''Mesh Network 7'''
 (not 1, 6, or 11).  This happens I think when I disconnect from my Access
 Point, which uses channel 7.  Screenshot coming.  Similarly, sometimes I
 see my AP tagged with channel 1, or 6, or 11, instead of the correct 7.
 (This is hinted to have happened long ago in an older ticket.)

 Weirdness !#2:  If XO starts up, or resumes from suspend, it first tries
 to find a Mesh network.  But if I impatiently click on my Access Point in
 Neighborhood view, XO successfully connects to my AP yet still appears to
 keep trying Mesh, forever.  I filed #8592 for a different aspect of this
 (it hogs CPU cycles).

 Weirdness !#3:  In frame, for design consistency, I think my AP icon
 should be labelled something constant like "My Network Connection", and
 the site-specific variable ssid should be moved into the secondary palette
 text near channel number and I.P. address.  Screenshot shows my ridiculous
 AP ssid in the primary palette text title.

 Weirdness !#4:  One time, in Neighborhood view after much clicking on the
 various icons, the icon for (only) Mesh Network 11 lost the text in its
 hover palette, showing a blank black box.  The loss was persistent until
 reboot.  Screenshot coming...

 Weirdness !#5:  Occasionally, XO creates or auto-connects to Mesh Network
 1 (or Simple Mesh) instead of my preferred AP which it normally has no
 trouble finding.  Screenshot coming.  There does not appear to be anything
 at Mesh 1; maybe the XO feels lonely and is fishing for company?  If I
 disconnect from Mesh 1, XO usually finds my AP on next try.

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