#10239 HIGH 10.1.2: XO-1 os301 segfault in Record activity

[Zarro Boogs per Child]

#10239: XO-1 os301 segfault in Record activity
---------------------------------------+------------------------------------
           Reporter:  Quozl            |       Owner:  dsd                              
               Type:  defect           |      Status:  new                              
           Priority:  high             |   Milestone:  10.1.2                           
          Component:  record-activity  |     Version:  Development build as of this date
         Resolution:                   |    Keywords:  os301                            
        Next_action:  package          |    Verified:  0                                
Deployment_affected:                   |   Blockedby:                                   
           Blocking:                   |  
---------------------------------------+------------------------------------
Changes (by mavrothal):

  * priority:  low => high


Comment:

 This is probably the same as http://bugs.sugarlabs.org/ticket/2041 which
 can be reproduced in a virgin os301 as follows from the UI.[[BR]]
 Record a clip.[[BR]]
 Play it back[[BR]]
 Delete it (screen is black)[[BR]]
 Press the "record" button -> activity quits[[BR]]
 If you have more than one clips recorded and you do that after you delete
 one the rest is lost. eg data loss.

 Record log shows[[BR]]

 {{{
 libv4l2: error setting pixformat: Device or resource busy
 0:04:03.682341811  2159  0x9e5c890 WARN                    v4l2
 gstv4l2object.c:1854:gst_v4l2_object_set_format:<camsrc> error: Device
 '/dev/video0' cannot capture at 640x480
 0:04:03.682884242  2159  0x9e5c890 WARN                    v4l2
 gstv4l2object.c:1854:gst_v4l2_object_set_format:<camsrc> error: Call to
 S_FMT failed for YUYV @ 640x480: Device or resource busy
 }}}



 and dmesg reports

 {{{ [  314.180184] Record <3830a6b[2508]: segfault at 10 ip b69d50e5 sp
 aeff9ee0 error 4 in libgstvideo4linux2.so[b69cc000+1b000] }}}

 I would hardly call the (UI) setting unusual and combining it with he data
 loss I would guess that priority probably needs to be raised to high

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