#10183 NORM Not Tri: Record-82 crashes on os204 while saving a just-recorded audio clip

[Zarro Boogs per Child]

#10183: Record-82 crashes on os204 while saving a just-recorded audio clip
---------------------------------------+------------------------------------
           Reporter:  mikus            |       Owner:  dsd                              
               Type:  defect           |      Status:  new                              
           Priority:  normal           |   Milestone:  Not Triaged                      
          Component:  record-activity  |     Version:  Development build as of this date
         Resolution:                   |    Keywords:                                   
        Next_action:  reproduce        |    Verified:  0                                
Deployment_affected:                   |   Blockedby:                                   
           Blocking:                   |  
---------------------------------------+------------------------------------
Changes (by Quozl):

  * next_action:  never set => reproduce


Comment:

 Replying to [comment:2 mikus]:
 > Replying to [comment:1 Quozl]:
 > > Record-82 cannot be installed because of #10186.  When Record-82 is
 installed using the chown workaround, this bug #10183 doesn't reproduce
 for me.
 > I install Activities manually, rather than through "software update".
 For me on os204, Record-82 always crashes in Audio, as soon as I click on
 the button to end the recording. (Record vanishes before it gets to save
 the clip).

 Which manual method do you use to install activities?  I ask this so that
 I can try that manual method and see if I can reproduce the symptom.

 > > Reviewed attachments that Mikus gave ... there's no explanation found
 for the vanishing.
 >
 > Can you please tell me how I should go about troubleshooting this
 problem.

 These are the methods I plan to use for troubleshooting:
  * reproduce the symptom myself on Record-82, e.g. by trying your manual
 install process,
  * attempt to reproduce the symptom on Record-81,
  * examine the source code changes from Record-81 to Record-82,
  * correlate the symptom against the source changes,
  * ensure the source that is unpacked on Mikus' system matches the source
 in Record-82,
  * compare the installed RPM list between Mikus' system and mine,
  * run the activity manually from Terminal so as to capture any unusual
 output,
  * run the activity with strace to capture any signals or exit status.

 Of these the ones that you could help with are:
  * does the symptom still occur for you without any undue effort?
  * could you tar up Activities/Record.activity and attach it?

 > > There's also a Record-79 in the journal, but that isn't likely to
 relate.
 > There should not be anything like that in the "Journal".  I normally
 keep my Journal VERY clean - I delete entries from it as soon as I have
 finished exercising any particular Activity.  And I haven't run Record-79
 on the XO-1.5 in days.

 That's interesting.  The shell.log shows there is a Record-79 present
 alongside Record-81, and then in a subsequent log it is shown as being
 alongside Record-82, and I presumed it was the Journal that held
 Record-79.  I have no explanation for why shell.log says this.

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