Hi Roland, My name is Clinton, and I'm one of the developers currently assigned to Shotwell.
I took a quick stab at trying to get the TombstoneTable into that same state (two rows with the same fully qualified path- and file-name, but with different IDs) wiht various combinations of importing and trashing, but regrettably, I couldn't. As far as it being a violation of the design, I'd need to ask around a bit, but (at least to the new guy) this doesn't seem to be terribly dangerous, since at this point, the image has been removed from the app already. If you do ever figure out how to trigger this reliably, please let us know. Outside of that, it _seems_ like we could avoid some badness here simply by checking if the file we're attempting to move is already gone, and if so, returning early from this method without asserting, since the task the method was supposed to accomplish is already done... I'll ask the Shotwell team lead about this later today, and if he agrees, we'll work on fixing this upstream as soon as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016859 Title: shotwell crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1016859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
