Version: 0.8.0 (using KDE KDE 3.4.3) Installed from: Debian testing/unstable Packages I just did some cleaning up of my digikam root tree. I switched from Picasa to digikam, and the directory structure was less than ideal. I removed empty dirs, dirs with just Picasa.ini files, etc. I moved some dirs that were children of pointless dirs to the root level, etc. So, when I restarted digikam, it noticed that the files weren't where they used to be. But instead of noticing that they had simply moved to a new location, it insisted on removing them from the database entirely. Frankly, that womps. Now I have to retag all of those images. digikam should store a hash of every photo in the database, and when it rescans the tree, it should notice if a file has moved or been renamed, and it should be able to cope with that by using the hash as the file's identity, not its filename or location in the directory tree. Please don't take this the wrong way; I really like digikam, and I want to help make it the best photo management app for Linux.
dupe of bug 110066
Thanks for that info Gilles. *** This bug has been marked as a duplicate of 110066 ***
Not reproducible using digiKam 7.0.0 beta1.