I did $ echo .dump | sqlite3 ~/.shotwell/data/photo.db | grep IMG_6016_CR2_shotwell.jpg INSERT INTO "TombstoneTable" VALUES(862,'/home/roland/Pictures/CanonT1i-images/2012/06/05/IMG_6016_CR2_shotwell.jpg',4635334,NULL,1340417401,0); INSERT INTO "TombstoneTable" VALUES(3083,'/home/roland/Pictures/CanonT1i-images/2012/06/05/IMG_6016_CR2_shotwell.jpg',4635334,'1b96783ac21dbdf66181828b8b49dbcb',1340417401,0); INSERT INTO "BackingPhotoTable" VALUES(1573,'/home/roland/Pictures/CanonT1i-images/2012/06/05/IMG_6016_CR2_shotwell.jpg',1339313673,4635334,3465,5202,1,0,1339313673);
so indeed there are two rows in the TombstoneTable with the same filename but different instance ids. Is this a violation of the design of the database? No idea exactly how things got into this state, except that I did delete some shotwell- generated files to clear up disk space at some point. -- 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
