Summary: | digiKam still crashing on startup with OpenSUSE | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Kenneth Ingham <kdebugs> |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | Keywords: | drkonqi |
Version: | 4.6.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.3.0 |
Description
Kenneth Ingham
2015-01-25 00:14:40 UTC
Here are relevant OpenSUSE packages installed: $ rpm -qa | egrep 'digikam|libkexiv|libexiv' | sort digikam-4.6.0-2.1.x86_64 digikam-debuginfo-4.6.0-2.1.x86_64 digikam-doc-4.6.0-2.1.noarch libexiv2-13-0.24-5.5.x86_64 libexiv2-13-debuginfo-0.24-5.5.x86_64 libexiv2-devel-0.24-5.5.x86_64 libkexiv2-11-14.12.1-1.1.x86_64 libkexiv2-11-debuginfo-14.12.1-1.1.x86_64 This is due to KDEbug message that KDE try to show in a GUI dialog instead console trace. As these message come from a separated thread and as X11 is non re-entrant, digiKAm crash. Solution : run kdebugdialog, and disable the option to wrap debug trace on a dialog. This problem is fixed definitively in KF5 port of digiKam as we don't use KDebug bu qDebug instead. Gilles Caulier *** This bug has been marked as a duplicate of bug 342010 *** Kenneth, did you read bug 342010 comment #2 and bug 342010 comment #6? Running kdebugdialog --fullmode and removing the message box from everything related to Digikam and KEXIV2 solved the problem. Thank you. Problem no longer exists since digiKam do not depends of libkexiv2 anymore. Gilles Caulier |