https://bugs.kde.org/show_bug.cgi?id=357577
--- Comment #11 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- No, debug symbols (as you get per -g in the CFLAGS) are necessary for a usable backtrace but not sufficient. You need to get theQt5 libs compiled "QT_DEBUG" defined and "QT_NO_DEBUG" _not_ defined, the same way you do when you want a KDE application to evaluate Q_ASSERT checks. See /usr/include/qt5/QtCore/qglobal.h ~line 665, where Q_ASSERT is handled. Normally Qt packages from distributions are compiled without QT_DEBUG and thus silently ignore such kinds of error situations. Maybe you have more luck by using a "developer build" of Qt and force digikam to use it by setting LD_LIBRARY_PATH into it. (see http://doc.qt.io/qt-5/configure-options.html and use the option "-developer-build" as suggested) -- You are receiving this mail because: You are watching all bug changes.