Version: digikam-0.10.0-6mdv2009.1 (using KDE 4.2.2) OS: Linux Installed from: Mandriva RPMs Digikam crashes always on startup, after the initialisation of the main screen (this is the message which is written in the startup-splash of Digikam). The following error message contains: "Digikam crashed and caused signal 11 (SIGSEGV)." The bug can be reproduced always as Digikam crashes all the time I try to start it. If I click on Details to get the details for the bug report I get another failure message that backtracing is impossible because Debugger gdb can not be found. Note: I am not using a camera or USB stick or something. These crashes happen, when I start Digikam on a normal way, like every other application. But also when I want to download pics from my camera (Nikon Coolpix P2) Digikam crashes in the same way. Used operating system: Mandriva 2009.1 Installed version: digikam-0.10.0-6mdv2009.1 some terminal output regarding installed libs and so on: rpm -qa | grep sqlite libsqlite0-2.8.17-10mdv2009.1 python-sqlite2-2.4.1-3mdv2009.1 mono-data-sqlite-2.2-2mdv2009.1 libsqlite3_0-3.6.11-2mdv2009.1 libsqlite3-devel-3.6.11-2mdv2009.1 sqlite-tools-2.8.17-10mdv2009.1 sqlite3-tools-3.6.11-2mdv2009.1 libqt3-sqlite-3.3.8b-14mdv2009.1 qt4-database-plugin-sqlite-4.5.0-3mdv2009.1 rpm -qa | grep digik libdigikamdatabase1-0.10.0-6mdv2009.1 digikam-0.10.0-6mdv2009.1 libdigikamcore1-0.10.0-6mdv2009.1 rpm -qa | grep kipi libkipi6-4.2.2-6mdv2009.1 libkipiplugins1-0.3.0-0.1mdv2009.1 kipi-common-4.2.3-0.1mdv2009.1 kipi-plugins-0.3.0-0.1mdv2009.1 Would be great if you could fix this because Digikam is the best Photo-database in the world!! Thanks & regards Steffen
please give us a gdb backtrace. Also, which Exiv2 library you use ? Gilles Caulier
I use the following EXIV2 libraries: libexiv2_5-0.18.1-1mdv2009.1 libkexiv2_7-4.2.2-6mdv2009.1 gdb backtrace not possible. Failure message: Debugger "gdb" can not be found. If I have to something to get the backtrace anyway, please explain how I get the backtrace
Just install GDB... and run digiKam as explained here : http://www.digikam.org/contrib Gilles Caulier
thanks for the advise. Here is the Terminal output of running Digikam with gdb. During this test, Digikam got stuck whilst the message "initialising main screen" (translated from german) came up in the splash. gdb digikam GNU gdb 6.8-6mdv2009.1 (Mandriva Linux release 2009.1) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i586-mandriva-linux-gnu"... (gdb) run Starting program: /usr/bin/digikam [Thread debugging using libthread_db enabled] [New Thread 0xb46b48e0 (LWP 2951)] [New Thread 0xb2fbeb90 (LWP 2962)] [New Thread 0xb235cb90 (LWP 2965)] [New Thread 0xb1b5bb90 (LWP 2966)] Detaching after fork from child process 2967. [New Thread 0xaea61b90 (LWP 2968)] [Thread 0xaea61b90 (LWP 2968) exited] Starting to load Plugins. === MarbleDirs: === Local Path: "/home/steffen/.marble/data" Plugin Local Path: "/home/steffen/.marble/plugins" Marble Data Path (Run Time) : "" Marble Data Path (Compile Time): "/usr/share/apps/marble/data" Marble Plugin Path (Run Time) : "" Marble Plugin Path (Compile Time): "/usr/lib/kde4/plugins/marble" System Path: "/usr/share/apps/marble/data" Plugin System Path: "/usr/lib/kde4/plugins/marble" =================== "CompassFloatItem.so" - "/usr/lib/kde4/plugins/marble/CompassFloatItem.so" Program received signal SIGSEGV, Segmentation fault. 0xb592bd1f in operator<< () from /usr/lib/libQtCore.so.4 Missing debug package(s), you should install: OpenEXR-debug-1.6.1-3mdv2009.0.i586 bzip2-debug-1.0.5-5mdv2009.1.i586 cyrus-sasl-debug-2.1.22-34.1mdv2009.1.i586 dbus-debug-1.2.4.4permissive-2mdv2009.1.i586 expat-debug-2.0.1-8mdv2009.1.i586 fontconfig-debug-2.6.0-5mdv2009.1.i586 freetype2-debug-2.3.9-1mdv2009.1.i586 gamin-debug-0.1.10-2mdv2009.1.i586 gcc-debug-4.3.2-5mnb2.i586 glib2.0-debug-2.20.1-1mdv2009.1.i586 glibc-debug-2.9-0.20081113.5mnb2.i586 gpsd-debug-2.38-1mdv2009.1.i586 gstreamer0.10-debug-0.10.22-2mdv2009.1.i586 gstreamer0.10-plugins-base-debug-0.10.22-3mdv2009.1.i586 gstreamer0.10-plugins-good-debug-0.10.14-1mdv2009.1.i586 ilmbase-debug-1.0.1-6mdv2009.1.i586 jasper-debug-1.900.1-5mdv2009.1.i586 kdebase4-runtime-debug-4.2.2-7mdv2009.1.i586 kdeedu4-debug-4.2.3-0.1mdv2009.1.i586 kdegraphics4-debug-4.2.2-6mdv2009.1.i586 kdegraphics4-debug-4.2.3-0.1mdv2009.1.i586 kdelibs4-debug-4.2.2-26mdv2009.1.i586 kdepimlibs4-debug-4.2.2-3mdv2009.1.i586 lcms-debug-1.18-1.1mdv2009.1.i586 libalsa2-debug-1.0.19-1mdv2009.1.i586 libexif-debug-0.6.17-4mdv2009.1.i586 libgphoto-debug-2.4.4-2mdv2009.1.i586 libice-debug-1.0.5-1mdv2009.1.i586 libjpeg-debug-6b-44mdv2009.1.i586 libmng-debug-1.0.10-9mdv2009.1.i586 liboil-debug-0.3.15-1mdv2009.1.i586 libpng-debug-1.2.35-1mdv2009.1.i586 libsm-debug-1.1.0-1mdv2009.1.i586 libtiff-debug-3.8.2-13mdv2009.1.i586 libtool-debug-2.2.6-6mdv2009.1.i586 libungif-debug-4.1.4-7mdv2009.1.i586 libx11-debug-1.2.1-1mdv2009.1.i586 libxau-debug-1.0.4-1mdv2009.1.i586 libxcb-debug-1.2-1mdv2009.1.i586 libxcursor-debug-1.1.9-3mdv2009.1.i586 libxdmcp-debug-1.0.2-6mdv2009.1.i586 libxext-debug-1.0.5-2mdv2009.1.i586 libxfixes-debug-4.0.3-4mdv2009.1.i586 libxi-debug-1.2.1-1mdv2009.1.i586 libxinerama-debug-1.0.3-2mdv2009.1.i586 libxml2-debug-2.7.3-2mdv2009.1.i586 libxrandr-debug-1.3.0-1mdv2009.1.i586 libxrender-debug-0.9.4-4mdv2009.1.i586 libxtst-debug-1.0.3-3mdv2009.1.i586 libxv-debug-1.0.4-2mdv2009.1.i586 openldap-debug-2.4.16-1mdv2009.1.i586 openssl-debug-0.9.8k-1.1mdv2009.1.i586 pcre-debug-7.8-3mdv2009.1.i586 phonon-debug-4.3.1-11mdv2009.1.i586 qt4-debug-4.5.0-3mdv2009.1.i586 sqlite3-debug-3.6.11-2mdv2009.1.i586 strigi-debug-0.6.4-2mdv2009.1.i586 xz-debug-4.999.8beta-0.2mdv2009.1.i586 zlib-debug-1.2.3-13mdv2009.1.i586 (gdb) bt #0 0xb592bd1f in operator<< () from /usr/lib/libQtCore.so.4 #1 0xb6e36301 in Marble::PluginManager::loadPlugins () from /usr/lib/libmarblewidget.so.4 #2 0xb6e37162 in Marble::PluginManager::PluginManager () from /usr/lib/libmarblewidget.so.4 #3 0xb6e3397a in Marble::LayerManager::LayerManager () from /usr/lib/libmarblewidget.so.4 #4 0xb6df12a6 in Marble::MarbleModel::MarbleModel () from /usr/lib/libmarblewidget.so.4 #5 0xb6dfb8ad in Marble::MarbleMap::MarbleMap () from /usr/lib/libmarblewidget.so.4 #6 0xb6dec31c in Marble::MarbleWidget::MarbleWidget () from /usr/lib/libmarblewidget.so.4 #7 0xb7284c1c in WorldMapWidget (this=0x9fa5fb8, w=256, h=256, parent=0x9faa6b0) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/worldmapwidget.cpp:77 #8 0xb7280f2f in ImagePropertiesGPSTab (this=0x9faa6b0, parent=0x5b75c085) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiesgpstab.cpp:96 #9 0xb7267216 in ImagePropertiesSideBar (this=0x9f47ae8, parent=0x9b0a548, splitter=0x5b75c085, side=1534443653, mimimizedDefault=true) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiessidebar.cpp:82 #10 0x0809a3e4 in ImagePropertiesSideBarDB (this=0x9f47ae8, parent=0x9b0a548, splitter=0x5b75c085, side=1534443653, mimimizedDefault=true) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiessidebardb.cpp:89 #11 0x0825bffe in DigikamView (this=0x9b0a548, parent=0x9b0ac70) at /usr/src/debug/digikam-0.10.0/digikam/digikamview.cpp:201 #12 0x082442e5 in Digikam::DigikamApp::setupView (this=0x9b35948) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:427 #13 0x0824fde3 in DigikamApp (this=0x9b35948) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:195 #14 0x082b44ff in main (argc=1, argv=0xbfc5a284) at /usr/src/debug/digikam-0.10.0/digikam/main.cpp:167
another one from the crash dialogue. Maybe it helps too: Anwendung: digiKam (digikam), Signal SIGSEGV [Current thread is 1 (Thread 0xb46c18e0 (LWP 19574))] Thread 4 (Thread 0xb2fcbb90 (LWP 19575)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb5556c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb564f8dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58285eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0x0828ed12 in Digikam::ScanController::run (this=0x9440298) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:412 #5 0xb58274df in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5553315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb564225e in clone () from /lib/i686/libc.so.6 Thread 3 (Thread 0xb2369b90 (LWP 19578)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb5556c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb564f8dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58285eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71c32fc in Digikam::LoadSaveThread::run (this=0x948b418) at /usr/src/debug/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:131 #5 0xb58274df in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5553315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb564225e in clone () from /lib/i686/libc.so.6 Thread 2 (Thread 0xb1b68b90 (LWP 19579)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb5556c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb564f8dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58285eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71c32fc in Digikam::LoadSaveThread::run (this=0x94811f0) at /usr/src/debug/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:131 #5 0xb58274df in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5553315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb564225e in clone () from /lib/i686/libc.so.6 Thread 1 (Thread 0xb46c18e0 (LWP 19574)): [KCrash Handler] #6 0xb5938d1f in operator<< () from /usr/lib/libQtCore.so.4 #7 0xb6e43301 in Marble::PluginManager::loadPlugins () from /usr/lib/libmarblewidget.so.4 #8 0xb6e44162 in Marble::PluginManager::PluginManager () from /usr/lib/libmarblewidget.so.4 #9 0xb6e4097a in Marble::LayerManager::LayerManager () from /usr/lib/libmarblewidget.so.4 #10 0xb6dfe2a6 in Marble::MarbleModel::MarbleModel () from /usr/lib/libmarblewidget.so.4 #11 0xb6e088ad in Marble::MarbleMap::MarbleMap () from /usr/lib/libmarblewidget.so.4 #12 0xb6df931c in Marble::MarbleWidget::MarbleWidget () from /usr/lib/libmarblewidget.so.4 #13 0xb7291c1c in WorldMapWidget (this=0x9915a40, w=256, h=256, parent=0x991a138) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/worldmapwidget.cpp:77 #14 0xb728df2f in ImagePropertiesGPSTab (this=0x991a138, parent=0x5b75c085) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiesgpstab.cpp:96 #15 0xb7274216 in ImagePropertiesSideBar (this=0x948bbb8, parent=0x9657bf8, splitter=0x5b75c085, side=1534443653, mimimizedDefault=true) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiessidebar.cpp:82 #16 0x0809a3e4 in ImagePropertiesSideBarDB (this=0x948bbb8, parent=0x9657bf8, splitter=0x5b75c085, side=1534443653, mimimizedDefault=true) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiessidebardb.cpp:89 #17 0x0825bffe in DigikamView (this=0x9657bf8, parent=0x949d8c0) at /usr/src/debug/digikam-0.10.0/digikam/digikamview.cpp:201 #18 0x082442e5 in Digikam::DigikamApp::setupView (this=0x948e5d8) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:427 #19 0x0824fde3 in DigikamApp (this=0x948e5d8) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:195 #20 0x082b44ff in main (argc=5, argv=0xbf865d84) at /usr/src/debug/digikam-0.10.0/digikam/main.cpp:167
Crash appear with marble widget not digiKam as well. Do you have installed marble-data from kde-edu package ? Gilles Caulier
the only things installed with marble in the name are: libmarblewidget4-4.2.3-0.1mdv2009.1 plasma-applet-bluemarble-4.2.2-1mdv2009.1 marble-common-4.2.3-0.1mdv2009.1
running stand alone version of marble crash or not ? Gilles Caulier
(In reply to comment #8) > running stand alone version of marble crash or not ? > > Gilles Caulier what do you mean? should I run "marble" in the terminal? If yes: "command not found"
AH ah !!! great install it and try again (:=))) Gilles
(In reply to comment #10) > AH ah !!! great install it and try again (:=))) > > Gilles I have installed marble but Digikam keeps on crashing Anwendung: digiKam (digikam), Signal SIGSEGV [Current thread is 1 (Thread 0xb46e28e0 (LWP 25108))] Thread 4 (Thread 0xb2de8b90 (LWP 25109)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb5577c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56708dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58495eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0x0828ed12 in Digikam::ScanController::run (this=0x88a61a0) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:412 #5 0xb58484df in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5574315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb566325e in clone () from /lib/i686/libc.so.6 Thread 3 (Thread 0xb238ab90 (LWP 25112)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb5577c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56708dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58495eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71e42fc in Digikam::LoadSaveThread::run (this=0x88e8118) at /usr/src/debug/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:131 #5 0xb58484df in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5574315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb566325e in clone () from /lib/i686/libc.so.6 Thread 2 (Thread 0xb1b89b90 (LWP 25113)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb5577c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56708dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58495eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71e42fc in Digikam::LoadSaveThread::run (this=0x88f0aa8) at /usr/src/debug/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:131 #5 0xb58484df in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5574315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb566325e in clone () from /lib/i686/libc.so.6 Thread 1 (Thread 0xb46e28e0 (LWP 25108)): [KCrash Handler] #6 0xb5959d1f in operator<< () from /usr/lib/libQtCore.so.4 #7 0xb6e64301 in Marble::PluginManager::loadPlugins () from /usr/lib/libmarblewidget.so.4 #8 0xb6e65162 in Marble::PluginManager::PluginManager () from /usr/lib/libmarblewidget.so.4 #9 0xb6e6197a in Marble::LayerManager::LayerManager () from /usr/lib/libmarblewidget.so.4 #10 0xb6e1f2a6 in Marble::MarbleModel::MarbleModel () from /usr/lib/libmarblewidget.so.4 #11 0xb6e298ad in Marble::MarbleMap::MarbleMap () from /usr/lib/libmarblewidget.so.4 #12 0xb6e1a31c in Marble::MarbleWidget::MarbleWidget () from /usr/lib/libmarblewidget.so.4 #13 0xb72b2c1c in WorldMapWidget (this=0x8d7a718, w=256, h=256, parent=0x8d7ee10) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/worldmapwidget.cpp:77 #14 0xb72aef2f in ImagePropertiesGPSTab (this=0x8d7ee10, parent=0x5b75c085) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiesgpstab.cpp:96 #15 0xb7295216 in ImagePropertiesSideBar (this=0x88ce800, parent=0x890b0d0, splitter=0x5b75c085, side=1534443653, mimimizedDefault=true) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiessidebar.cpp:82 #16 0x0809a3e4 in ImagePropertiesSideBarDB (this=0x88ce800, parent=0x890b0d0, splitter=0x5b75c085, side=1534443653, mimimizedDefault=true) at /usr/src/debug/digikam-0.10.0/libs/imageproperties/imagepropertiessidebardb.cpp:89 #17 0x0825bffe in DigikamView (this=0x890b0d0, parent=0x890af38) at /usr/src/debug/digikam-0.10.0/digikam/digikamview.cpp:201 #18 0x082442e5 in Digikam::DigikamApp::setupView (this=0x88988c0) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:427 #19 0x0824fde3 in DigikamApp (this=0x88988c0) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:195 #20 0x082b44ff in main (argc=5, argv=0xbfa887a4) at /usr/src/debug/digikam-0.10.0/digikam/main.cpp:167
maybe I have done something wrong? I'm not very useful in computers :-))
I have a solution: deinstall of libmarblewidget4-4.2.3-0.1mdv2009.1 including, Marble and Digikam, re-installation of Digikam and Marble.