#9896 HIGH Not Tri: Ad-hoc network fails when XO goes into sleep

[Zarro Boogs per Child]

#9896: Ad-hoc network fails when XO goes into sleep
------------------------------------+---------------------------------------
           Reporter:  edmcnierney   |       Owner:                
               Type:  defect        |      Status:  new           
           Priority:  high          |   Milestone:  Not Triaged   
          Component:  not assigned  |     Version:  1.5-B3        
         Resolution:                |    Keywords:  network ad-hoc
        Next_action:  never set     |    Verified:  0             
Deployment_affected:                |   Blockedby:                
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by mikus):

 There are various situations.  Here is a "consistent" situation:

 1) Booted XO-1.5 (Murga, os62).  Started Terminal.[[BR]]
 2) Started ad-hoc network from XO-1.5 Frame icon - ad-hoc network icon
 showed up in XO-1.5 Neighborhood View - the XO-1.5 was assigned an IP
 address[[BR]]
 3) Booted XO-1 (Gaiss, os10).  Clicked on ad-hoc network icon in XO-1
 Neighborhood View.  The XO-1 connected to the netwok, and was assigned an
 IP address.
 3) Let the XO-1.5 suspend (power light pulsing, USB keyboard dead).[[BR]]
 4) Used power button to wake up XO-1.5.  Ad-hoc network icon disappeared
 from XO-1.5 Neighborhood View, and from XO-1.5 Frame.  **BUG**:  this left
 the XO-1.5 Frame without any icon whatsoever for wireless.[[BR]]
 5) Took 'olpc-log' on XO-1.5.[[BR]]
 6) BTW, the XO-1 still has the "connected" ad-hoc network icon in its
 Neighborhood View and in its Frame.  But #9896 is not about the XO-1, nor
 about os10.

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