#10166 NORM Not Tri: Write sharing failure

[Zarro Boogs per Child]

#10166: Write sharing failure
--------------------------------------+-------------------------------------
 Reporter:  tabitha                   |                 Owner:  uwog         
     Type:  defect                    |                Status:  new          
 Priority:  normal                    |             Milestone:  Not Triaged  
Component:  write-activity (abiword)  |               Version:  not specified
 Keywords:                            |           Next_action:  never set    
 Verified:  0                         |   Deployment_affected:               
Blockedby:                            |              Blocking:               
--------------------------------------+-------------------------------------
 We're not sure if this the right place to report this, but here goes.

 We tried out Write version 60 and it started and could write. Could
 collaborate (mesh11) and all write fine. Managed to get 4 XO-1.0s using
 Write all by joining from the neighbourhood view. Sometimes the update of
 content was sluggish. They collaborated for a while but then some quit
 with no warning.

 Logs from original author (the one that initiated the shared document) are
 attached.

 How do we diagnose this in the future? Should we capture the network
 traffic?

 XO 1.0
 Martin's os802b6

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