#8972 HIGH Not Tri: Write Activity (v. 60) freeze with .doc and .odt documents

[Zarro Boogs per Child]

#8972: Write Activity (v. 60) freeze with .doc and .odt documents
------------------------------------------------+---------------------------
           Reporter:  jasg                      |       Owner:  morgs        
               Type:  defect                    |      Status:  new          
           Priority:  high                      |   Milestone:  Not Triaged  
          Component:  write-activity (abiword)  |     Version:  not specified
         Resolution:                            |    Keywords:               
        Next_action:  never set                 |    Verified:  0            
Deployment_affected:  Paraguay                  |   Blockedby:               
           Blocking:                            |  
------------------------------------------------+---------------------------
Changes (by rgs1):

 * cc: tomeu (added)


Comment:

 I tried this patch with build 767 and Write Activitiy version 60 (acording
 to ~/Activities/Write.activity/activity/activity.info).

 I used the following steps to see if it solves the problem (of opening the
 document as plain text and/or crashing):

 1) downloaded to the journal the word file attached to this ticket

 2) I resumed the file with Write and without doing any changes to it I
 closed the Write Activity

 3) I tried to re-resume the file from the journal and I got the following
 error in /var/log/messages:

 Nov 21 15:37:07 localhost kernel: [ 4455.261663] Escribir <8d807[2300]:
 segfault at 34 ip b5e5922b sp bff7c0f8 error 4 in
 libabiword-2.6.so[b59af000+5bd000]

 After that I found the .odt file in the datastore directory and I copied
 it to my regular laptop and tried to open it with Open Office (using
 Ubuntu). When trying to open it I got a "General Error" message but the
 file finally got opened and I got a badly constructed version of the file
 (you can read some parts of it).

 I am attaching the .odt file copied from the datastore (in case anyone
 wants to take a look at it, I am not familiar with the inner structure of
 odt files to tell what went wrong) and Write's log.

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