great it woas fixed in f-spot (0.4.4-1ubuntu4) and after this intrepid was migrated to 0.5.0.2-0ubuntu4 . seems like somebody forgot to send this bug upstream?
great it woas fixed in f-spot (0.4.4-1ubuntu4) and after this intrepid was migrated to 0.5.0.2-0ubuntu4 . seems like somebody forgot to send this bug upstream?