*** This bug is a duplicate of bug 199496 ***
https://bugs.launchpad.net/bugs/199496
thanks for your report, that's known and it's now fixed on hardy,
thanks.
** Changed in: f-spot (Ubuntu)
Status: Incomplete => Invalid
** This bug has been marked a duplicate of bug 199496
Tomboy.e
Ok, the repro scenario is really easy: I started from the command line
as you describe ("f-spot --debug &> fspot-log.txt"). Then click the
File menu, then select Quit. It dies with a segv. The fspot-log.txt
file is attached.
** Attachment added: "fspot-log.txt"
http://launchpadlibrarian.net
Thanks for your bug report. Could you please run f-spot as: f-spot
--debug &> fspot-log.txt and attach that file to the report? Thanks in
advance.
** Attachment removed: "CoreDump.gz"
http://launchpadlibrarian.net/13416072/CoreDump.gz
** Changed in: f-spot (Ubuntu)
Importance: Undecided =>
