Version: (using KDE 4.2.4) Compiler: gcc 4.4.1 OS: Linux Installed from: SuSE RPMs Digikam compiled from recent trunk (rev 1033809) crashes occasional during startup. It does not happen every time, maybe one out of four. I haven't been able to notice any consistent thing that would trigger the crash (after crash, next time it may startup normally, or then it may crash again). Unfortunately I haven't been able to cause the crash when running Digikam in gdb, so I cannot provide a gdb stack trace. I'll include output of Digikam before the crash and info provided by the KDE crash handler. Since this happens only occasionally, my guess would be a concurrency and timing related problem? (I have a dual-core processor, and hardware concurrency has a tendency to show these bugs more easily.)
Created attachment 37550 [details] Crash log
Created attachment 37551 [details] Output of Digikam before the crash
Dario, libc crash... Gilles
Pasting backtrace inline: --- Thread 1 (Thread 0x7f22979f2760 (LWP 7104)): #0 0x00007f2290bdccf1 in nanosleep () from /lib64/libc.so.6 #1 0x00007f2290bdcaec in sleep () from /lib64/libc.so.6 #2 0x00007f229382b95f in ?? () from /usr/lib64/libkdeui.so.5 #3 0x00007f229382c2ba in KCrash::defaultCrashHandler(int) () from /usr/lib64/libkdeui.so.5 #4 <signal handler called> #5 0x00007f2290b6d645 in raise () from /lib64/libc.so.6 #6 0x00007f2290b6ec33 in abort () from /lib64/libc.so.6 #7 0x00007f2290ba98e8 in ?? () from /lib64/libc.so.6 #8 0x00007f2290baf108 in ?? () from /lib64/libc.so.6 #9 0x00007f2290bb0c66 in free () from /lib64/libc.so.6 #10 0x00007f22929f38c7 in ?? () from /usr/lib64/libQtCore.so.4 #11 0x00007f224e471c61 in ?? () from /usr/lib64/kde4/kipiplugin_jpeglossless.so #12 0x00007f224e469588 in ?? () from /usr/lib64/kde4/kipiplugin_jpeglossless.so #13 0x000000000068139d in Digikam::DigikamApp::slotKipiPluginPlug (this=0xd525a0) at /home/bitti/nobackup/src/digikam/graphics/digikam/digikam/digikamapp.cpp:2303 #14 0x000000000066968f in Digikam::DigikamApp::qt_metacall (this=0xd525a0, _c=QMetaObject::InvokeMetaMethod, _id=32, _a=0x7fff142e5680) at /home/bitti/nobackup/src/digikam/digikambuild/digikam/digikam/digikamapp.moc:215 #15 0x00007f22929e8454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #16 0x00007f22963aab7b in KIPI::PluginLoader::replug (this=0x4d4c690) at /home/bitti/nobackup/src/digikam/kdelibbuild/libs/libkipi/libkipi/pluginloader.moc:95 #17 0x00007f22963abfe3 in KIPI::PluginLoader::loadPlugins (this=0x4d4c690) at /home/bitti/nobackup/src/digikam/kdegraphics/libs/libkipi/libkipi/pluginloader.cpp:271 #18 0x0000000000680b79 in Digikam::DigikamApp::loadPlugins (this=0xd525a0) at /home/bitti/nobackup/src/digikam/graphics/digikam/digikam/digikamapp.cpp:2246 #19 0x000000000066b7e3 in DigikamApp (this=0xd525a0) at /home/bitti/nobackup/src/digikam/graphics/digikam/digikam/digikamapp.cpp:240 #20 0x0000000000784138 in main (argc=1, argv=0x7fff142e6028) at /home/bitti/nobackup/src/digikam/graphics/digikam/digikam/main.cpp:163 -- To me it looks like a Kipi-plugins related issue (jpeg loseless). The backtrace could be related to the one in https://bugs.kde.org/show_bug.cgi?id=200159#c12 If you can reproduce the crash at will (or you experience this regularly), can you install the "kipi-plugins-debuginfo" package and post a complete backtrace here? Thanks
Also ensure that you updated to a recent version of libkipi and kipi-plugins. Maybe some binary incompatibility.
Hmmm... Marchel, you may have something there. I compile libkipi and kipi-plugins from svn. However, on my KDE 4.2.4 machine, Digikam's cmake does not find necessary libraries to compile calendar kipi-plugin (is some extra configuration needed, I think I should have all necessary lib and devel packages installed?). So, Digikam build is configured not to compile the calendar plugin. Now it seems that when I run Digikam, it still tries to load the calendar plugin and find the KDE 4.2.4 version. I'm not sure if that might be the reason for my problems. Or maybe I'm configuring something wrong in the build process, digikam.org's compilation pages (http://www.digikam.org/drupal/download?q=download/KDE4) are not very complete in this respect, I think. Especially if and when I want to install Digikam and necessary libraries somewhere else than /usr/lib (I wouldn't like to put development stuff from svn there).
Matti, remove your CMakeCache.txt file from your root source code dir, and start cmake again... Gilles Caulier
is this still valid for you ?
Nicolas, I had complete forgotten this bug report. It can be closed, I managed to get rid of the problem with help from Marcel. I had installed Digikam to a non-default location and apparently it managed to find a couple of old kipi-plugins from elsewhere in the system. Matti