#10121 NORM Not Tri: Unexpected auto-reconnect behavior (XO-1)

[Zarro Boogs per Child]

#10121: Unexpected auto-reconnect behavior (XO-1)
--------------------------+-------------------------------------------------
 Reporter:  mikus         |                 Owner:               
     Type:  defect        |                Status:  new          
 Priority:  normal        |             Milestone:  Not Triaged  
Component:  not assigned  |               Version:  not specified
 Keywords:                |           Next_action:  never set    
 Verified:  0             |   Deployment_affected:               
Blockedby:                |              Blocking:               
--------------------------+-------------------------------------------------
 Using os140py on XO-1.  Went to a place with several locked APs.  Clicked
 on one (let's call it A9).  It asked for key, and I entered one.  It still
 did not connect.  I asked the people there, and found that I had clicked
 on the wrong icon.  So I clicked on another AP icon (let's call it A7).
 It asked for key (I entered the same one) and it connected.  All good.

 Had occasion to bring up a Gnome application.  Exited Sugar via My
 Settings panel.  In Gnome, ran application.  Exited Gnome by clicking on
 "Switch to Sugar".  Once in Sugar, I happened to look at Neighbohood View
 -- it was trying to auto-connect the wireless to A9.  It asked for key, I
 clicked "cancel" -- only then did it attempt to auto-connect to A7 -- that
 worked, without asking for a key.

 [[BR]]What I did not expect was that the XO would slavishly *repeat* my
 mistake (and first try auto-connect with the wrong AP) when Sugar came up
 again.  Since the last AP to which it had been connected was A7, I would
 have expected it to try auto-connect first with A7.

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