Version: (using KDE 3.5.8) Installed from: Fedora RPMs OS: Linux Unfortunately I have very little to add. As soon as I type digikam from the konsole, I got the segmentation fault error. This is occuring both as normal user and as root. I'm using a clean Fedora 8 installation and I've already tried to remove and re-install the digikam rpm several times but with no luck. digikam was used to work properly in the past (probably before I did some updates). The rest of the system is working well and stable. I'm willing to provide any further information upon request. Thanks for your help.
We definitively need more information to track this problem down: a) which version of digikam are you using? b) are there any messages on the konsole before the segmentation fault? c) To really find the source of the problem, a proper backtrace is needed, See: http://www.digikam.org/?q=contrib under "If you are experiencing crashes with digiKam" However, to ensure a useful backtrace, one has to compile digikam with debugging information. Usually this is non-trivial for someone who has never installed software from source (but we can guide you through the build procedure on the users mailing list, if you want. See http://www.digikam.org/?q=download/svn under "Install digiKam in your Home Directory" for instructions). But maybe there are already rpm's with a debug build available for fedora? Best, Arnd
Thanks Arnd for the fast reply. Here you have your answer: a) digikam-0.9.3-1.fc8 b) none c) I'm a software developer, so no problem to install software from source... but I need some times to do it. I'll report on that as soon as possible.
Two more things: i) what happens if you move your current image collection out of the way and start digikam again? ii) which version of exiv2 is used (See "About" under digikam, if you get that far ;-), or which version of exiv2 is installed on your systems?
To check if the problem was somehow related with my image collection, I created a temporary new user (a completely empty home dir) and tried to run digikam. Same result! I can't get the version of exiv2 clicking on About simply because I can't see any windows. But looking at the rpm package exiv2 should be 0.1.6 Thanks
Antonio, if you run digiKam from a console, are you any debug messages ? If you run digiKam into GDB, are you a suitable backtrace of the crash ? Note : look in HACKING file for details... Gilles Caulier
This is all I get running digikam from the command line: [toto@localhost ~]$ digikam Segmentation fault this is for the debugger [toto@localhost ~]$ gdb digikam GNU gdb Red Hat Linux (6.6-40.fc8rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... warning: Missing the separate debug info file: /usr/lib/debug/.build-id/00/59aa8cd3533012fb7be96d4e62a5ce0a417cf2.debug (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/digikam warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ac/2eeb206486bb7315d6ac4cd64de0cb50838ff6.debug (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. 0x002bea70 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2 (gdb) I do believe that the binaries in the RPM were not build with debug symbols. thanks
Created attachment 23143 [details] debug output for showfoto
I don't know if it can be of any use, but also showfoto crashes while starting. In this case Kcrash is able to catch the crashing and the debug info are attached.
you need to recompile digiKam with debug symbol. Bactrace is not suitable... Gilles Caulier
I'm trying to install from source following the instruction available on the web site, but the digikam configure fails giving this error message: ... checking if Qt needs -ljpeg... no checking for rpath... yes checking for KDE... libraries /usr/lib, headers /usr/include/kde checking if UIC has KDE plugins available... no configure: error: you need to install kdelibs first. If you did install kdelibs, then the Qt version that is picked up by this configure is not the same version you used to compile kdelibs. The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the _same Qt version_, compiled with the _same compiler_ and the same Qt configuration settings. Of course, kdelibs are installed on my system but I didn't compile them by self. Is there a way to force the configure script to continue? thanks
Really ??? Witch linux box you use ? I have never seen something like that (:=)))) Gilles
I'm using a fresh install of Fedora 8. All packages have been installed using RPMs. antonio
Antonio, Some fresh news about this entry ? Gilles Caulier
after the latest updates everything is back to work! thanks for asking...
Ok thanks Gilles
Same crash here under Debian unstable - but I believe it is connected with GLX: Last output before crash: Found dcraw version: 8.83 versions: Qt: 3.3.8b KDE: 3.5.9 digiKam: 0.9.3 exiv2: 0.16-4 Any hints? Mplayer has the same behaviour - so it might be a flaw in my personal installation.