id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,distribution,status_field 1824,Blank/corrupt entries at end of Journal,garycmartin,martin.langhoff,"Testing Sugar 0.87.7 in an F11 VM. Looking through existing entries in Journal shows a number of 'invisible' slots at the end of the Journal that I think aligns with broken/empty Journal items (that can be left hanging around after Sugar crashes). Mousing over the blank area left causing partial widget redraws for the missing items (see attached screen shot). Either Journal should list broken entries as broken objects (allowing the user to know there was some breakage and delete them manually); or the datastore should be cleaning up and/or not be returning empty/broken data to the Journal to incorrectly display. Found this shell.log traceback which may be related: {{{ Traceback: File "".../install/lib/python2.6/site-packages/jarabe/journal/listview.py"", line 425, in update_dates path = tree_model.get_path(next_iter) TypeError: iter should be a GtkTreeIter }}} On later examining of the Journal these blank items are now not showing anymore, so perhaps there is indeed some background clean-up of broken entries going on.",defect,closed,Unspecified by Maintainer,Unspecified,Sugar,Unspecified,Unspecified,obsolete,,sascha_silbe alsroot,Unspecified,Unconfirmed