Bug 103323

Summary:	digikam crashes at startup
Product:	[Applications] digikam	Reporter:	tudor <tudor>
Component:	Portability-Runtime	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	caulier.gilles
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:	7.6.0
Sentry Crash Report:

Description tudor 2005-04-05 22:57:40 UTC

Version:            (using KDE KDE 3.3.2)
Installed from:    Gentoo Packages
Compiler:          gcc-3.3.5-r1 
OS:                Linux

Every time I start Digikam-0.7.2 it crashes. when I start it from Konsole it says: 

digikam: WARNING: [void AlbumFolderView::loadAlbumState()] Failed to open albumtreestate.bin

The splash screen is shown and "Loading Cameras" and then it crashes each time. I've recompilote digikam libgphoto2 gphoto2 and the other dependencies. Installing Digikam 0.6.2 works fine. But 0.7.2 doesn't. 

The KDE-Crashmanager says :

(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 29387)]
0x4e2267e8 in waitpid ()
   from /lib/libpthread.so.0
#0  0x4e2267e8 in waitpid () from /lib/libpthread.so.0
#1  0x4ef05124 in ?? () from /usr/kde/3.3/lib/libkdecore.so.4
#2  0x4ee28790 in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.3/lib/libkdecore.so.4



On my other PC I installed Digikam 0.7.2 too and it works fine. I am using Gentoo on both PCs.

Thanks a lot

Comment 1 Renchi Raju 2005-04-06 01:42:11 UTC

sounds like a broken installation. compile with a debugging support and send the full backtrace.

Comment 2 tudor 2005-04-06 10:42:58 UTC

how can I compile with a debugging support

Comment 3 Tom Albers 2005-04-06 10:52:27 UTC

compile like normal, only add the option --enable-debug=full to the ./configure command.

Comment 4 tudor 2005-04-06 12:22:09 UTC

I am using Gentoo so the .configure ist generated automatically when I do "emerge digikam". So I did "USE="debug" EXTRA_ECONF="--enable-debug=full" emerge digikam" When I start Digikam now the KDE-Crash-Manager shows the same thing-no changes.

Thanks

Comment 5 Tom Albers 2005-04-06 12:42:52 UTC

Please ensure that "nostrip" is in your FEATURES.
(copied from http://amarok.kde.org/wiki/index.php/Installation_HowTo)

Comment 6 tudor 2005-04-06 22:26:22 UTC

I did recompile with nostrip but no changes. Perhaps it's because of my use-flags? 

USE="divx4linux i8x0 win32codecs real dvdread pic X -gtk -gnome sdl alsa arts jack kde qt xine pda usb ppds foomaticdb gimpprint cupssse sse2 mmx dvd cdr gimpprint samba wifi mplayer sdk"

Comment 7 Renchi Raju 2005-04-16 19:09:46 UTC

compile from source (without using gentoo ebuilds) and send us a backtrace. thanks

Comment 8 tudor 2005-04-16 19:25:07 UTC

everything works fine now thank you
I recompiled my Gentoo installation

Comment 9 Renchi Raju 2005-04-16 19:26:55 UTC

thanks for letting us know