#9559 NORM 1.5-F11: os33 - Journal misbehaving

[Zarro Boogs per Child]

#9559: os33 - Journal misbehaving
--------------------------------+-------------------------------------------
           Reporter:  mikus     |       Owner:  marco                            
               Type:  defect    |      Status:  new                              
           Priority:  normal    |   Milestone:  1.5-F11                          
          Component:  sugar     |     Version:  Development build as of this date
         Resolution:            |    Keywords:                                   
        Next_action:  diagnose  |    Verified:  0                                
Deployment_affected:            |   Blockedby:                                   
           Blocking:            |  
--------------------------------+-------------------------------------------

Comment(by sayamindu):

 Hmm, this is a tricky issue. While the knee-jerk reaction would be to
 simply not display the journal entries that are damaged, some of the
 entries might actually still work (for example, clicking on the "blank"
 entry in my synthetically damaged journal did start the activity
 correctly). It would be almost impossible to figure out the level of
 "damage" to the underlying datastore/filesystem from Sugar level, so as a
 result, it would be impossible to figure out which damaged entries to show
 and which to hide.
 I'll try to start a discussion on upstream sugar list about this.

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