$ digikam KCrash: Application 'digikam' crashing... KCrash cannot reach kdeinit, launching directly. I have the same problem -> http://bugs.kde.org/show_bug.cgi?id=112845 Several tests i did were: 1. deleting the entire digikam configuration - didnt help. 2. deleting digikam.db files and .thumbnail folder - didnt help. 3. testing if application will load with empty pictures folder - succeeded. 4. testing if application will load with 1 picture inside - application crashed I've also made this tests and digikam react in the same way, so maybe the cause is that gcc4 patch mentioned at the end that bug I've lineked above. //sorry for my english, I know it isn't good... emerge --info Portage 2.1_pre4-r1 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.6-r3, 2.6.15.1 i686) ================================================================= System uname: 2.6.15.1 i686 AMD Sempron(tm) 2600+ Gentoo Base System version 1.12.0_pre16 ccache version 2.4 [enabled] dev-lang/python: 2.3.5-r2, 2.4.2-r1 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-4 -Os -pipe -fomit-frame-pointer -msse -mmmx -m3dnow -fno-ident -DNDEBUG -DG_DISABLE_ASSERT -DNO_DEBUG -s" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-4 -Os -pipe -fomit-frame-pointer -msse -mmmx -m3dnow -fno-ident -DNDEBUG -DG_DISABLE_ASSERT -DNO_DEBUG -s" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks nodoc sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.prz.rzeszow.pl/" LANG="pl_PL" LC_ALL="pl_PL" LDFLAGS="-Wl,-O1 -s" LINGUAS="pl" MAKEOPTS="-j1 -s" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X aac acpi alsa avi berkdb bindist bitmap-fonts cdparanoia cdr crypt dga dri dvd encode extramodules fbcon firefox fortran ftp gdbm gif glx gpm gtk gtk2 imlib jpeg kde libg++ libwww lm_sensors mad mikmod mmx mmxext motif mp3 ncurses nls nptl nptlonly nvidia ogg oggvorbis opengl oss pdflib perl pic png python qt quicktime readline reiserfs sdl sndfile sox sse ssl symlink tcpd truetype truetype-fonts type1-fonts unicode userlocales vorbis win32codecs wxwindows xml2 xpm xrandr xv zlib elibc_glibc input_devices_mouse input_devices_keyboard kernel_linux linguas_pl userland_GNU video_cards_nvidia" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS
First: Please file your bugs here, not at bugs.kde.org unless it's a wish or you're absolutely sure that is in upstream issue. It's costs their time dealing with your invalid bug reports and the kde devs probably don't even run Gentoo. Second: It's not bound to the gcc compatibility patch. Don't assume something and let us look bad, you apparently don't have an idea about. Please post the output of ldd /usr/lib/libdigikam.so | grep exif and ldd /usr/lib/libkexif.so | grep exif
(In reply to comment #1) > First: Please file your bugs here, not at bugs.kde.org unless it's a wish or > you're absolutely sure that is in upstream issue. It's costs their time dealing > with your invalid bug reports and the kde devs probably don't even run Gentoo. I didn't file my bug at bugs.kde.org (I even don't have account there). Nir Dremer filed it not me. I've just found it via google (after searching on gentoo forum and gentoo bugs). > Second: It's not bound to the gcc compatibility patch. Don't assume something > and let us look bad, you apparently don't have an idea about. I've just wrote that maybe it's that patch (as Nir Dremer found the cause of his problems in it) maybe didn't mean propably, it's sth different for me. EOT, I don't want to argue ;) > > Please post the output of > > ldd /usr/lib/libdigikam.so | grep exif libkexif.so.1 => /usr/lib/libkexif.so.1 (0xb777b000) libexif.so.10 => /usr/lib/libexif.so.10 (0xb69ef000) > > and > > ldd /usr/lib/libkexif.so | grep exif libexif.so.10 => /usr/lib/libexif.so.10 (0xb723d000)
(In reply to comment #2) > I didn't file my bug at bugs.kde.org (I even don't have account there). Nir > Dremer filed it not me. I've just found it via google (after searching on > gentoo forum and gentoo bugs). Sorry. I assume it's not the case a revdep-rebuild is in order? If not this may be bound to -Os. Try -O2 instead. And please try the current ebuild, 0.8.0 isn't even in the tree anymore.
Didin't help. Still: $ digikam KCrash: Application 'digikam' crashing... KCrash cannot reach kdeinit, launching directly. I'm usging: # emerge -vp digikam [ebuild R ] media-gfx/digikam-0.8.1-r1 USE="-arts -debug -nfs -xinerama" 0 kB
Version 0.8.1-r1 also crashes for me. Solution: emerge =libexif-0.5.12-r3 cd /usr/lib ln -s libexif.so.9.1.2 libexif.so.10
I expierienced exaclty the same behaviour and struggled with it a few hours. This is not a CLFAGS problem. see http://bugs.gentoo.org/show_bug.cgi?id=118556 Developers, please track down the problem or mask =libexif-0.6.12-r4.
Tha(In reply to comment #6) > I expierienced exaclty the same behaviour and struggled with it a few hours. > This is not a CLFAGS problem. > see http://bugs.gentoo.org/show_bug.cgi?id=118556 > > Developers, please track down the problem or mask =libexif-0.6.12-r4. > That's fix the problem. Big thanks to you. (I'm wonder why i didn'y find this on bugzilla before)
