https://bugs.kde.org/show_bug.cgi?id=430858
--- Comment #2 from Maik Qualmann <metzping...@gmail.com> --- This problem can only occur if the similarity database has not been initialized. Which cannot actually not occur because the pointer is always assigned a value. I suspect there was a crash while scanning and parts of digiKam were already in delete mode. The scanner thread then encountered zo the pointer that had already been deleted. So we need a better backtrace, don't forget "bt" next time. Maik -- You are receiving this mail because: You are watching all bug changes.
