I opened an upstream bugreport: https://bugs.kde.org/show_bug.cgi?id=323062 At least a workaround is described there (go back digikam4.db file from backup). The problem is not fully understood though. I have no problem though if you want to close the debian bugreport. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/