I really would like to, but even though I searched I could not identify the offending image. >From the stacktrace when run with "-v" it looks like f-spot DOES detect that >the meta data looks bogus, but then does not handle the situation fully:
$ f-spot -verbose [Info 01:02:03.718] Initializing Mono.Addins [Warn 01:02:06.365] Metadata of file file:///.,,/DSCN0140-1.jpg may be corrupt, refusing to write to it, falling back to XMP sidecar. Exception in Gtk# callback delegate.... then removing the file stated above: $ f-spot -verbose [Info 01:05:21.965] Initializing Mono.Addins Exception in Gtk# callback delegate... I could not triage which image/database entry leads to the crash, while the above mentioned image imported cleanly on a separate machine. (All machines running maverick 10.10, current f-spot) -- f-spot crashes when image has wrong date https://bugs.launchpad.net/bugs/653327 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
