Summary: | Digikam crash on launch | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | kaulian <kaulian> |
Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, caulier.gilles |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Sentry Crash Report: |
Description
kaulian
2009-09-08 19:42:35 UTC
Sound like Glibc issue, aready reported in this room. A settings is on from KDE 4.3 env. with glibc to hack all indeep problems. Gilles Caulier Mh, that would be bug 196207. However thread 2 looks suspicious too: Thread 2 (Thread 0xa8aefb70 (LWP 20276)): #0 0xb5612395 in QString::operator= () from /usr/lib/libQtCore.so.4 #1 0xb565490a in QIODevice::setErrorString () from /usr/lib/libQtCore.so.4 Yes it's can be the same bug... I try with ~ =] export MALLOC_CHECK_=0 before launch digikam and that work no crash *** This bug has been marked as a duplicate of bug 196207 *** Fixed with https://bugs.kde.org/show_bug.cgi?id=196207 |