#5770 NORM Never A: Browse failure playing USB-key .wav file through Journal, works if through Browse itself

[Zarro Boogs per Child]

#5770: Browse failure playing USB-key .wav file through Journal, works if through
Browse itself
--------------------+-------------------------------------------------------
 Reporter:  rbh00   |       Owner:  jg            
     Type:  defect  |      Status:  new           
 Priority:  normal  |   Milestone:  Never Assigned
Component:  distro  |     Version:                
 Keywords:          |    Verified:  0             
 Blocking:          |   Blockedby:                
--------------------+-------------------------------------------------------
 On a fresh boot I inserted a USB key with a number of .wav files on its
 root.  I opened the Journal Activity and clicked on USB.  I chose one of
 the .wav files and clicked on that little rect-within-circle at the right.
 The Browse Activity began to start and never completed starting.  It
 remained at "Starting..." for minutes on end, in fact, until reboot.

 I have successfully played the same .wav file from the same USB key by
 starting the Browse Activity and surfing to file:///media/LEXAR and
 clicking the same .wav file.

 To reproduce the bug:
 1. Boot.
 2. Insert USB key with .wav files on it.
 3. Open the Journal Activity.
 4. Note the USB icon at the bottom and click on it.
 5. Choose a .wav file and click on that line's righthand icon.
 6. Note that on the Home screen the Browse icon appears and flashes.
 7. Note that mouseover of the Browse icon shows "Starting...".
 8. Note that after a while the USB key light flashes for perhaps a minute.
 9. Using top(1) note that a python process takes ~80% cpu during the
 flashing and for seconds afterward; then jffs2_gcd_mtd0 takes 80% for a
 while; then nothing much.
 10. On Home screen note that Browse is still "Starting...".

 To reproduce the successful operation:
 1. Boot.
 2. Insert the USB key (either before or after boot).
 3. Open the Browse Activity.
 4. Surf to file:///media/LEXAR (in the case of my key).
 5. Click on the same .wav file tried above.
 6. (Note from the USB light that the file appears to be read in completely
 before audio starts.)
 7. Note that the .wav file plays wonderfully well.
 8. (Note from top that totem-plugin-vi is taking 80%cpu.)
 9. Note that the "Reload" button works fine.
 10. Note that the psychedelic screen works fine.  It remains after the
 selection completes playing.  I bet totem-plugin-vi does this.
 11. But note that Ctrl-W does not end the Browse window that plays the wav
 and go back to the Browse window that shows file:///media/LEXAR (it
 should).  Ctrl-Q does quit Browse, though.

 But even so, the startup time, the time between when I clicked on the wav
 file and the tune started playing, was >120s, over two minutes!  Maybe 20s
 of this is readin time for the .wav, but that happens late in the
 interval.  On another try the time was about 70s.  Maybe the file was
 buffered at that attempt though.  ... Nope, on a fresh boot, the same
 procedure takes 65s from click to music.  But of course THIS IS TOO LONG.
 I can't reproduce my >120s assertion.

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