#11012 NORM Not Tri: Data lost if collaboration is terminated and re-established

[Zarro Boogs per Child]

#11012: Data lost if collaboration is terminated and re-established
------------------------------------+---------------------------------------
           Reporter:  sridhar       |       Owner:                                         
               Type:  defect        |      Status:  new                                    
           Priority:  normal        |   Milestone:  Not Triaged                            
          Component:  not assigned  |     Version:  1.5/1.0 Software Build os860 aka 10.1.3
         Resolution:                |    Keywords:                                         
        Next_action:  diagnose      |    Verified:  0                                      
Deployment_affected:                |   Blockedby:                                         
           Blocking:                |  
------------------------------------+---------------------------------------
Changes (by greenfeld):

  * next_action:  never set => diagnose


Comment:

 Reproduced on 11.2.0 os23.  Tried to add a "DD" on the first laptop to
 cause a double update collision, but the second XO would not load data
 into Write beyond what it resumed from its journal prior to attempting to
 load from the other system.  (The latter could also be local Wifi
 conditions acting up again.)

 This is an interesting mix of things, perhaps somewhat intentional and
 unintentional, and I vaguely recall seeing this before.  Sugar
 automatically sharing resumed activities is a known issue/feature.

 I do not believe Sugar has a mechanism in place to warn that one or both
 versions of the file differ, and allow one to be preferred, or how this
 could be exposed in a Children-friendly manner.  Perhaps we should force a
 keep/copy prior to resuming a Shared activity?

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