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

Zarro Boogs per Child bugtracker at laptop.org
Tue Jun 21 00:44:15 EDT 2011


#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
 Keywords:                |           Next_action:  never set                              
 Verified:  0             |   Deployment_affected:                                         
Blockedby:                |              Blocking:                                         
--------------------------+-------------------------------------------------
 Tested on an XO-1.5 with XO-AU OS 10.1.3-au2 (basically the same as OLPC
 OS 10.1.3).

 General summary:

  1. A shares an activity
  1. B connects to A's shared instance
  1. Collaborative work is done by A and B
  1. A closes the activity
  1. B continues to work on the activity (maybe they didn't realise that A
 has left)
  1. A shares again
  1. B connects
  1. Everything B has worked on since A left the first time is lost

 This example uses the Write activity, but it can happen with any activity:

  1. A begins activity
  1. A types something (text is “AA” now)
  1. A shares the activity
  1. B joins activity
  1. B types something (text is “AABB” now)
  1. A closes activity (Text saved in A’s journal is AABB)
  1. B continues to write something (text is “AABBCC” now)
  1. B also closes activity (Text saved in B’s journal is AABBCC)
  1. Now B opens the same activity from B’s journal. B is able to see the
 text AABBCC now.
  1. B closes the activity.
  1. Now A opens the activity from journal. Text is AABB now.
  1. A shares the activity again.
  1. B joins the activity from the neighbourhood view since it is shared.
 Text in B’s XO is AABB now.
  1. A and B close the activity.
  1. Now when B opens the activity from the journal again, only AABB is
 seen (text CC is lost).

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


More information about the Bugs mailing list