f-spot crashes on specific picture(s)

[coffeemonk]

Binary package hint: f-spot

f-spot consistently crashes on a few specific pictures in my collection.

Steps to Reproduce (in browse mode):
1) browse to nearby the crashy picture.
2) expose the tag bar
3a) select with mouse the picture next to the crashy picture, move selection to crashy picture with arrow keys
OR
3b) directly select crashy picture with mouse

Steps to Reproduce (in view/edit mode):
1) browse to nearby the crashy picture
2a) enter view/edit mode by double-clicking picture next to crashy picture, then move to crashy picture using arrow key
OR
2b) double-click directly on crashy picture to enter in view/edit mode

A few other things that trigger this crash:
1) expose tag bar when multiple pictures (including crashy one) are selected in browse mode.
2) select multiple pictures (including crashy one) when tag bar is exposed in browse mode.

I just tried running "Sync Catalog to Photos" and thought that had fixed the issue for one of the images, but it crashed on another image, then crashed on the original image again after restarting f-spot.

I have built 0.6.2 from source, and it is also exhibiting this crash behavior.

I will attempt to attach a couple of the crashy pictures to this report.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: f-spot 0.6.1.5-2ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sun Jun 6 09:07:22 2010
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: f-spot

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.