Let me know if you need more details.

I cannot see any digiKam code relevant there. Do you install digikam-debug package ?

Gilles Caulier

I added the package digikam-dbg, here is the same crash with it:

----------------------------------

Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fa8904857e0 (LWP 18305))]

Thread 10 (Thread 0x7fa8746a9710 (LWP 18306)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fa889b3072b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x232b5b0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x232b5b0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00000000006e1d9b in Digikam::ScanController::run (this=0x232b2b0) at /build/buildd/digikam-1.2.0/digikam/scancontroller.cpp:516
#4  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x232b2b0) at thread/qthread_unix.cpp:248
#5  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 9 (Thread 0x7fa870d9d710 (LWP 18308)):
#0  0x00007fa8898a23f5 in __pthread_mutex_lock (mutex=0x7fa86406f668) at pthread_mutex_lock.c:61
#1  0x00007fa885ec5ee3 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#2  0x00007fa885ec6318 in ?? () from /lib/libglib-2.0.so.0
#3  0x00007fa885ec68fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0x00007fa889c4d566 in QEventDispatcherGlib::processEvents (this=0x25b5e70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#5  0x00007fa889c22992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#6  0x00007fa889c22d6c in QEventLoop::exec (this=0x7fa870d9cd70, flags=) at kernel/qeventloop.cpp:201
#7  0x00007fa889b2cd59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#8  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x2602850) at thread/qthread_unix.cpp:248
#9  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 8 (Thread 0x7fa86bfff710 (LWP 18309)):
#0  0x00007fa8898a23f5 in __pthread_mutex_lock (mutex=0x25ac9a8) at pthread_mutex_lock.c:61
#1  0x00007fa885ec65d1 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fa885ec68fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fa889c4d566 in QEventDispatcherGlib::processEvents (this=0x25ba2d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007fa889c22992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fa889c22d6c in QEventLoop::exec (this=0x7fa86bffed70, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fa889b2cd59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x25bd170) at thread/qthread_unix.cpp:248
#8  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#9  0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 7 (Thread 0x7fa86b7fe710 (LWP 18310)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fa889b3072b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x269a318, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x269a318, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fa88d489532 in Digikam::LoadSaveThread::run (this=0x269a300) at /build/buildd/digikam-1.2.0/libs/threadimageio/loadsavethread.cpp:131
#4  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x269a300) at thread/qthread_unix.cpp:248
#5  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 6 (Thread 0x7fa86affd710 (LWP 18311)):
#0  0x00007fa8898a23d4 in __pthread_mutex_lock (mutex=0x2655da8) at pthread_mutex_lock.c:51
#1  0x00007fa885ec5ee3 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#2  0x00007fa885ec6318 in ?? () from /lib/libglib-2.0.so.0
#3  0x00007fa885ec68fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0x00007fa889c4d566 in QEventDispatcherGlib::processEvents (this=0x2676e60, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#5  0x00007fa889c22992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#6  0x00007fa889c22d6c in QEventLoop::exec (this=0x7fa86affcd70, flags=) at kernel/qeventloop.cpp:201
#7  0x00007fa889b2cd59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#8  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x2653590) at thread/qthread_unix.cpp:248
#9  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7fa86a7fc710 (LWP 18312)):
#0  0x00007fa885ec1033 in g_main_context_query () from /lib/libglib-2.0.so.0
#1  0x00007fa885ec639c in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fa885ec68fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fa889c4d566 in QEventDispatcherGlib::processEvents (this=0x26790d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007fa889c22992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fa889c22d6c in QEventLoop::exec (this=0x7fa86a7fbd70, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fa889b2cd59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x2653150) at thread/qthread_unix.cpp:248
#8  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#9  0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7fa85aeb0710 (LWP 18319)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fa889b3072b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x2b84ee8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x2b84ee8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fa88d489532 in Digikam::LoadSaveThread::run (this=0x2b84ed0) at /build/buildd/digikam-1.2.0/libs/threadimageio/loadsavethread.cpp:131
#4  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x2b84ed0) at thread/qthread_unix.cpp:248
#5  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fa8605a8710 (LWP 18326)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fa889b3072b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x2f78f88, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x2f78f88, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fa88d489532 in Digikam::LoadSaveThread::run (this=0x2f78f70) at /build/buildd/digikam-1.2.0/libs/threadimageio/loadsavethread.cpp:131
#4  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x2f78f70) at thread/qthread_unix.cpp:248
#5  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fa859c41710 (LWP 18327)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fa889b3072b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x3021568, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x3021568, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fa88d489532 in Digikam::LoadSaveThread::run (this=0x3021550) at /build/buildd/digikam-1.2.0/libs/threadimageio/loadsavethread.cpp:131
#4  0x00007fa889b2f775 in QThreadPrivate::start (arg=0x3021550) at thread/qthread_unix.cpp:248
#5  0x00007fa88989f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007fa888bd669d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa8904857e0 (LWP 18305)):
[KCrash Handler]
#5  QIcon (this=0x7fff5a15f990, other=...) at image/qicon.cpp:531
#6  0x00007fa88ab08184 in QAction::icon (this=<value optimized out>) at kernel/qaction.cpp:735
#7  0x00007fa88ebc4b7e in KIPI::PluginLoader::Info::icon() const () from /usr/lib/libkipi.so.7
#8  0x00007fa88ebc6359 in KIPI::ConfigWidget::ConfigWidget(QWidget*) () from /usr/lib/libkipi.so.7
#9  0x00007fa88ebc6519 in KIPI::PluginLoader::configWidget(QWidget*) () from /usr/lib/libkipi.so.7
#10 0x00000000004d95ca in SetupPlugins (this=0x62b9dd0, parent=<value optimized out>) at /build/buildd/digikam-1.2.0/utilities/setup/setupplugins.cpp:73
#11 0x00000000004b758b in Setup (this=0x4ad7880, parent=<value optimized out>) at /build/buildd/digikam-1.2.0/utilities/setup/setup.cpp:224
#12 0x00000000004b8970 in Digikam::Setup::exec (parent=0x23bd0a0, page=Digikam::Setup::LastPageUsed) at /build/buildd/digikam-1.2.0/utilities/setup/setup.cpp:336
#13 0x0000000000692571 in Digikam::DigikamApp::slotSetup (this=0x23bd0a0, _c=QMetaObject::InvokeMetaMethod, _id=104467744, _a=0x7fff5a1602d0)
    at /build/buildd/digikam-1.2.0/digikam/digikamapp.cpp:2114
#14 Digikam::DigikamApp::qt_metacall (this=0x23bd0a0, _c=QMetaObject::InvokeMetaMethod, _id=104467744, _a=0x7fff5a1602d0)
    at /build/buildd/digikam-1.2.0/obj-x86_64-linux-gnu/digikam/digikamapp.moc:222
#15 0x00007fa889c36e3f in QMetaObject::activate (sender=0x314e200, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x65cd230) at kernel/qobject.cpp:3293
#16 0x00007fa88ab08032 in QAction::triggered (this=0x7fff5a15f990, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
#17 0x00007fa88ab0a0ab in QAction::activate (this=0x314e200, event=<value optimized out>) at kernel/qaction.cpp:1255
#18 0x00007fa88af4939d in QMenuPrivate::activateCausedStack (this=<value optimized out>, causedStack=..., action=0x314e200, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1011
#19 0x00007fa88af4edda in QMenuPrivate::activateAction (this=0x44c5c60, action=0x314e200, action_e=QAction::Trigger, self=<value optimized out>) at widgets/qmenu.cpp:1103
#20 0x00007fa88bb50cee in KMenu::mouseReleaseEvent (this=0x44d4580, e=0xa8) at ../../kdeui/widgets/kmenu.cpp:471
#21 0x00007fa88ab64582 in QWidget::event (this=0x44d4580, event=0x7fff5a160f20) at kernel/qwidget.cpp:7998
#22 0x00007fa88af50f9b in QMenu::event (this=0x44d4580, e=0x7fff5a160f20) at widgets/qmenu.cpp:2414
#23 0x00007fa88ab0e22c in QApplicationPrivate::notify_helper (this=0x207bf40, receiver=0x44d4580, e=0x7fff5a160f20) at kernel/qapplication.cpp:4300
#24 0x00007fa88ab14ecb in QApplication::notify (this=0x7fff5a161c40, receiver=0x44d4580, e=0x7fff5a160f20) at kernel/qapplication.cpp:3865
#25 0x00007fa88ba74526 in KApplication::notify (this=0x7fff5a161c40, receiver=0x44d4580, event=0x7fff5a160f20) at ../../kdeui/kernel/kapplication.cpp:302
#26 0x00007fa889c2406c in QCoreApplication::notifyInternal (this=0x7fff5a161c40, receiver=0x44d4580, event=0x7fff5a160f20) at kernel/qcoreapplication.cpp:704
#27 0x00007fa88ab140ae in QCoreApplication::sendEvent (receiver=0x44d4580, event=0x7fff5a160f20, alienWidget=0x0, nativeWidget=0x44d4580, buttonDown=<value optimized out>, 
    lastMouseReceiver=<value optimized out>, spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#28 QApplicationPrivate::sendMouseEvent (receiver=0x44d4580, event=0x7fff5a160f20, alienWidget=0x0, nativeWidget=0x44d4580, buttonDown=<value optimized out>, lastMouseReceiver=<value optimized out>, 
    spontaneous=true) at kernel/qapplication.cpp:2965
#29 0x00007fa88ab943dd in QETWidget::translateMouseEvent (this=0x44d4580, event=<value optimized out>) at kernel/qapplication_x11.cpp:4302
#30 0x00007fa88ab928ac in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff5a161840) at kernel/qapplication_x11.cpp:3501
#31 0x00007fa88abbe882 in x11EventSourceDispatch (s=0x207fc50, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#32 0x00007fa885ec28c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0x00007fa885ec6748 in ?? () from /lib/libglib-2.0.so.0
#34 0x00007fa885ec68fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0x00007fa889c4d513 in QEventDispatcherGlib::processEvents (this=0x20416d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#36 0x00007fa88abbe46e in QGuiEventDispatcherGlib::processEvents (this=0x7fff5a15f990, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007fa889c22992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#38 0x00007fa889c22d6c in QEventLoop::exec (this=0x7fff5a161b70, flags=) at kernel/qeventloop.cpp:201
#39 0x00007fa889c26aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#40 0x000000000077fa9b in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/digikam-1.2.0/digikam/main.cpp:193

----------------------------------

Does this help?

This looks like a binary compatibility issue. I remember that I had a similar backtrace in such a case.

Check libkipi. Do you have more than one instance of this lib installed on your computer ?

Gilles Caulier

According to Synaptic, I have libkipi7 (Ubuntu version package 4:4.4.2-0ubuntu1).
Nothing else.

I can confirm this (latest libs and digiKam of course).
Gilles, Johannes,

it always helps to delete the digikamrc if users report errors we are not able to reproduce. For me the crash appears now with a fresh digikamrc file.

I also noticed another problem: I installed svn trunk on a friends machine to test something, after that I went back to digiKam 1.2.0 (archlinux package).

Suddently the digikamrc is invalid and we need to create a new file.
Have we changed some variables in digikamrc? Maybe this is relevant to the switch to the new database back-end system?

Anyway I'll confirm this bug now, maybe I'll find the time to fix this bug today.

Ok I guess the problem is the icons in the plugins list someone added on the past.
If I uncheck a plugin and re-enter the settings dialog, digiKam crashes.
After restart, I can go to the settings dialog again, but the icon is missing in the kipi plugins tab for the unchecked plugin.

I guess this is the issue... I'll check this now.

I remember to have fixed this problem in the past :

http://websvn.kde.org/trunk/KDE/kdegraphics/libs/libkipi/libkipi/pluginloader.cpp?r1=1056488&r2=1056487&pathrev=1056488

Look also BUG #216790

Gilles Caulier

I already modified this code and checked every single pointer and data structure I could think of 

(
d->m_plugin,  d->m_plugin->actions(), 
d->m_plugin->actions().isEmpty(), 
d->m_plugin->actions()[0] == 0, 
d->m_plugin->actions()[0]->icon().isNull()
), 

but still it crashes. I don't know why...?

Created attachment 43655 [details]
Icons

It funny that you speak of icons, since all uncheck options do not have any icons. See attachment in comment #11.

Yes and this is the problem... the icons can not be found and we have a null pointer issue. After restart, at least the pointers seem to be valid again, but with an "error" icon assigned.

ok, but this should be in another minor bug report since it does not crash DigiKam.

No because it is the same bug :-)
It is because the absence of the icon that digiKam crashes. On restart, the action is not loaded at all and therefore no invalid icon pointer exists.

ok, got it.
Let me know if you want me to test something else.

SVN commit 1130288 by apol:

Make the service icon to be the the default icon for the plugin and use the first action as a fallback (in case we have one).

CCMAIL: caulier.gilles@gmail.com


 M  +4 -2      pluginloader.cpp


--- trunk/KDE/kdegraphics/libs/libkipi/libkipi/pluginloader.cpp #1130287:1130288
@@ -167,8 +167,10 @@

 QIcon PluginLoader::Info::icon() const
 {
-    if (d->m_plugin) return QIcon(d->m_plugin->actions()[0]->icon());
-    else return KIcon(d->m_service->icon());
+    if(d->m_service->icon().isEmpty() && d->m_plugin)
+        return QIcon(d->m_plugin->actions()[0]->icon());
+    else
+        return KIcon(d->m_service->icon());
 }

 Plugin* PluginLoader::Info::plugin() const

Andi,

Commit #1130288 fix the problem ?

Gilles

I will test this as soon as I'm alive again (I was jogging :-))

Yes seems to be fixed!

*** Bug 232792 has been marked as a duplicate of this bug. ***

*** Bug 243275 has been marked as a duplicate of this bug. ***

SVN commit 1144959 by cgilles:

more check there


 M  +9 -2      pluginloader.cpp


--- trunk/KDE/kdegraphics/libs/libkipi/libkipi/pluginloader.cpp #1144958:1144959
@@ -168,10 +168,17 @@
 QIcon PluginLoader::Info::icon() const
 {
    if(d->m_service->icon().isEmpty() && d->m_plugin)
-        return QIcon(d->m_plugin->actions()[0]->icon());
+    {
+        if (d->m_plugin->actions()[0])
+            return d->m_plugin->actions()[0]->icon();
    else
-        return KIcon(d->m_service->icon());
+            return QIcon();
 }
+    else
+    {
+        return QIcon(d->m_service->icon());
+    }
+}

 Plugin* PluginLoader::Info::plugin() const
 {

Created attachment 48668 [details]
New crash information added by DrKonqi

digikam (1.3.0) on KDE Platform 4.4.92 (KDE 4.4.92 (KDE 4.5 RC2)) using Qt 4.6.3

I've compiled digikam 1.3.0 and it still crashes when calling configuration through the Setting->Configuration.

-- Backtrace (Reduced):
#7  0x00007f020fcd4586 in KIPI::PluginLoader::Info::icon (this=0xa9bf18) at /var/tmp/portage/kde-base/libkipi-4.5.9999/work/libkipi-4.5.9999/libs/libkipi/libkipi/pluginloader.cpp:171
#8  0x00007f020fcd63a9 in PluginCheckBox (this=0x4f5cfa0, parent=<value optimized out>) at /var/tmp/portage/kde-base/libkipi-4.5.9999/work/libkipi-4.5.9999/libs/libkipi/libkipi/pluginloader.cpp:357
#9  ConfigWidget (this=0x4f5cfa0, parent=<value optimized out>) at /var/tmp/portage/kde-base/libkipi-4.5.9999/work/libkipi-4.5.9999/libs/libkipi/libkipi/pluginloader.cpp:382
#10 0x00007f020fcd6569 in KIPI::PluginLoader::configWidget (this=<value optimized out>, parent=0x27b6a50)
    at /var/tmp/portage/kde-base/libkipi-4.5.9999/work/libkipi-4.5.9999/libs/libkipi/libkipi/pluginloader.cpp:346
#11 0x00000000004dc00a in SetupPlugins (this=0x4ac6db0, parent=<value optimized out>) at /var/tmp/portage/media-gfx/digikam-1.3.0/work/digikam-1.3.0/utilities/setup/setupplugins.cpp:73

*** Bug 245628 has been marked as a duplicate of this bug. ***

*** Bug 245775 has been marked as a duplicate of this bug. ***

*** Bug 245776 has been marked as a duplicate of this bug. ***

Created attachment 53551 [details]
New crash information added by DrKonqi

digikam (1.5.0) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0

- What I was doing when the application crashed:

as soon as i try to open the settings dialog, the application crashes, this bug still appears in both 1.40 and 1.5.0. im using kde 4.5.3, and it  appears this bug regressed somehow.

-- Backtrace (Reduced):
#6  QAction::icon (this=0x91) at kernel/qaction.cpp:736
#7  0x00007faf520e6a4e in KIPI::PluginLoader::Info::icon (this=0xab71f8) at ../../../../libs/libkipi/libkipi/pluginloader.cpp:171
#8  0x00007faf520e8861 in PluginCheckBox (this=0x5d32d50, parent=<value optimized out>) at ../../../../libs/libkipi/libkipi/pluginloader.cpp:357
#9  KIPI::ConfigWidget::ConfigWidget (this=0x5d32d50, parent=<value optimized out>) at ../../../../libs/libkipi/libkipi/pluginloader.cpp:382
#10 0x00007faf520e8a09 in KIPI::PluginLoader::configWidget (this=<value optimized out>, parent=0x5d31920) at ../../../../libs/libkipi/libkipi/pluginloader.cpp:346

Created attachment 53694 [details]
New crash information added by DrKonqi

digikam (1.6.0) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:
1. Open configuration
2. Uncheck some kipi plugin
3. close configuration
4. try to reopen configuration


Happend 3 times out of 4

-- Backtrace (Reduced):
#7  0x04aff161 in QIcon::QIcon(QIcon const&) () from /usr/lib/libQtGui.so.4
#10 0x0011e868 in KIPI::ConfigWidget::ConfigWidget(QWidget*) () from /usr/lib/libkipi.so.7
#11 0x0011ea24 in KIPI::PluginLoader::configWidget(QWidget*) () from /usr/lib/libkipi.so.7
#12 0x0810f060 in Digikam::SetupPlugins::SetupPlugins (this=0x126ff4, parent=0x0) at /home/piret/devel/digikam-1.6.0/utilities/setup/setupplugins.cpp:73
#13 0x080e8a42 in Digikam::Setup::Setup (this=0xad3f880, parent=0x8c060a0) at /home/piret/devel/digikam-1.6.0/utilities/setup/setup.cpp:237

Crash is in libkipi from KDE core (kdegraphics). With KDE 4.5.3, i fixed this problem.

Update KDE4 and try again

Gilles Caulier

(In reply to comment #30)
> Crash is in libkipi from KDE core (kdegraphics). With KDE 4.5.3, i fixed this
> problem.
> 
> Update KDE4 and try again

Updated, still occurs.
Compiled lipkipi, digikam & kipi-plugins  from trunk, still crash.

But seems like my system is not complete: for some reason the "Themes" menu is disabled in digikam. Might it be one of the causes?

Gert

*** Bug 263871 has been marked as a duplicate of this bug. ***

I still have the crash.
Digikam 1.8.0  from tarball,  kdegraphics libs compiled from svn:


digiKam version 1.8.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: No
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.19
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.5.5 (KDE 4.5.5)
LibKExiv2: 1.2.0
LibKdcraw: 1.3.0
LibLCMS: 118
LibLensFun: 0.2.5-1 - internal library
LibLqr: internal library
LibPGF: 6.09.44 - internal library
LibPNG: 1.2.44
LibQt: 4.7.0
LibRaw: 0.12.5
LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble widget: 0.10.3
Parallelised demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.8
LibKipi: 1.2.0

Gert,

I fixed a problem with kipi-plugins actions management in digiKam core with this commit in 2.0.0:

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/e395cd0b3d998e7dec5bf3551ce015da6def5eaf

I backported it to 1.9.0 :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/97534ddb6558504bfada066deba5f5c322e1da86

Please checkout digiKam fro git (1.9.0) and try again.

Gilles Caulier

*** Bug 281250 has been marked as a duplicate of this bug. ***

*** Bug 282781 has been marked as a duplicate of this bug. ***

Are You going to re-open it? I still get the crash, digikam-sc compiled from git master, with -DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS:BOOL=1

no. it's a bug from libkipi, fixed since few months now. Your local version of libkipi is too old. update it to solve the crash

Gilles Caulier

Really? As much as I can tell, I have libkipi compiled from git master.

digiKam version 2.2.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.21.1
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.7.1 (4.7.1)
LibKExiv2: 2.1.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.0
LibLCMS: 118
LibPGF: 6.11.32 - internal library
LibPNG: 1.2.44
LibQt: 4.7.2
LibRaw: 0.13.8
LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.12.0 (stable release)
Parallelized demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.10.1
LibKface: 2.0.0
LibKipi: 1.3.0
LibOpenCV: 2.1.0
Libface: 0.2

Check if you have more than libkipi shared lib installed on your computer...

Gilles Caulier

gert@host:~$ locate libkipi.so
/home/gert/devel/digikam/build/lib/libkipi.so
/home/gert/devel/digikam/build/lib/libkipi.so.8
/home/gert/devel/digikam/build/lib/libkipi.so.8.0.1
/usr/lib/libkipi.so
/usr/lib/libkipi.so.8
/usr/lib/libkipi.so.8.0.1
gert@host:~$

according to aptitude libkipi8 is not installed

apt-get -s install libkipi8
NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libkipi-data
The following NEW packages will be installed:
  libkipi-data libkipi8
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Inst libkipi-data (4:4.7.1-0ubuntu1~natty1~ppa1 Kubuntu Backports:11.04/natty [all])
Inst libkipi8 (4:4.7.1-0ubuntu1~natty1~ppa1 Kubuntu Backports:11.04/natty [i386])
Conf libkipi-data (4:4.7.1-0ubuntu1~natty1~ppa1 Kubuntu Backports:11.04/natty [all])
Conf libkipi8 (4:4.7.1-0ubuntu1~natty1~ppa1 Kubuntu Backports:11.04/natty [i386])

Created attachment 66645 [details]
New crash information added by DrKonqi

The program crashed when I went to open the settings. I did disable a bunch of plugins earlier in the session, so I guess it's the same issue as reported, but apparently not really fixed. I installed this two days ago from your website.

*** Bug 297629 has been marked as a duplicate of this bug. ***