svn: crash when opening editor
Locked
12
12
svn: crash when opening editor
 
|
Hi,
When I open the editor digikam immediately crashes. I started the start-script from command line and got the following: - - - - kdeinit: Shutting down running client. --------------------------------- It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/daniel/.DCOPserver_venus__0 and start dcopserver again. --------------------------------- KDE Daemon (kded) already running. kbuildsycoca running... Reusing existing ksycoca Found dcraw version: 8.82 QFile::open: No file name specified QFile::open: No file name specified terminate called after throwing an instance of 'Exiv2::Error' what(): Die Rgistrierung für das HerstellerfeldInfo ist voll KCrash: Application 'digikam' crashing... - - - - (the text after what() means: the registry for the ManufacturersfieldInfo is full) The KDE-Crash-Window showed the following: - - - - Überprüfung der Systemkonfiguration beim Start deaktiviert. [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb58e36d0 (LWP 3868)] [New Thread 0xb4e01b90 (LWP 3889)] [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb59118f5 in raise () from /lib/libc.so.6 #8 0xb59131e1 in abort () from /lib/libc.so.6 #9 0xb5b08380 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #10 0xb5b05c25 in ?? () from /usr/lib/libstdc++.so.6 #11 0xb5b05c62 in std::terminate () from /usr/lib/libstdc++.so.6 #12 0xb5b05d8a in __cxa_throw () from /usr/lib/libstdc++.so.6 #13 0xb7301a09 in Exiv2::ExifTags::registerMakerTagInfo () from /usr/lib/libexiv2.so.2 #14 0xb72f9a5b in Exiv2::SonyMakerNote::RegisterMn::RegisterMn () from /usr/lib/libexiv2.so.2 #15 0xb2d0e5cf in ?? () from /usr/lib/libexiv2.so.0 #16 0xb2d2c1a5 in ?? () from /usr/lib/libexiv2.so.0 #17 0xb2d62ff4 in ?? () from /usr/lib/libexiv2.so.0 #18 0x08c05cf0 in ?? () #19 0xbfae9e68 in ?? () #20 0xb2ca4198 in _init () from /usr/lib/libexiv2.so.0 Backtrace stopped: frame did not save the PC - - - - If you need more info, I can deliver it tomorrow... good night Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
Daniel,
The crash is relevant of Exiv2 library. Which version you use ? Gilles 2008/2/22, Daniel Bauer <[hidden email]>: Hi, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
On Saturday 23 February 2008 10.33:18, Gilles Caulier wrote:
> Daniel, > > The crash is relevant of Exiv2 library. Which version you use ? > > Gilles > Hello, good morning Gilles exiv2 -V gives: exiv2 0.16 which exiv2 gives: /usr/bin/exiv2 I compiled exiv2 with "./configure --prefix=/usr" (without prefix it would have been installed in /usr/local/, which I thought was wrong...) kind regards Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
On Sat, 23 Feb 2008, Daniel Bauer wrote:
> On Saturday 23 February 2008 10.33:18, Gilles Caulier wrote: > > Daniel, > > > > The crash is relevant of Exiv2 library. Which version you use ? > > > > Gilles > > > > Hello, good morning Gilles > > exiv2 -V gives: > exiv2 0.16 > > which exiv2 gives: > /usr/bin/exiv2 > > I compiled exiv2 with "./configure --prefix=/usr" (without prefix it would > have been installed in /usr/local/, which I thought was wrong...) Don't you install digikam & the rest to some other place? I.e. the script compile_exiv2.sh at http://www.digikam.org/?q=download/svn puts stuff to DIGIKAMDEST (which I would recommend to be something accessible as user, and not root). What is the output of which digikam ldd `which digikam` ? Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
On Saturday 23 February 2008 13.35:16, Arnd Baecker wrote:
> On Sat, 23 Feb 2008, Daniel Bauer wrote: > > On Saturday 23 February 2008 10.33:18, Gilles Caulier wrote: > > > Daniel, > > > > > > The crash is relevant of Exiv2 library. Which version you use ? > > > > > > Gilles > > > > Hello, good morning Gilles > > > > exiv2 -V gives: > > exiv2 0.16 > > > > which exiv2 gives: > > /usr/bin/exiv2 > > > > I compiled exiv2 with "./configure --prefix=/usr" (without prefix it > > would have been installed in /usr/local/, which I thought was wrong...) > > Don't you install digikam & the rest to some other place? Yes, I use the script from digikam-page for local install in home directory, with DIGIKAMDEST=/home/daniel/digikam/progs > I.e. the script compile_exiv2.sh > at http://www.digikam.org/?q=download/svn > puts stuff to DIGIKAMDEST > (which I would recommend to be something accessible as > user, and not root). Yes, I would use this as I did earlier, but dev.robotbattle.com/exiv2/trunk still seems not to work... Now I copied the exiv2-0.16 folder (from the tar-file) to my home/digikam directory and compiled again with prefix=/home/daniel/digikam/progs and run make and make install as user. But digikam still crashed on opening the editor. So I run the compile-digikam.sh again, but the crash still occurs... The output of which exiv2 is now /home/daniel/digikam/progs/bin/exiv2 > > What is the output of > which digikam > ldd `which digikam` > ? I also have installed the stable digikam-Version from opensuse rpms. I always had this, so in case of something not working in the svn version I could still fall back to the stable one. This is the reason why I install svn in the home directory as user... Maybe you see this in the output of those commands: daniel@venus:~> which digikam /home/daniel/digikam/progs/bin/digikam daniel@venus:~> ldd `which digikam` linux-gate.so.1 => (0xffffe000) libdigikam.so.0 => /home/daniel/digikam/progs/lib/libdigikam.so.0 (0xb7ac9000) libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb7a39000) libkabc.so.1 => /opt/kde3/lib/libkabc.so.1 (0xb798a000) libvcard.so.0 => /opt/kde3/lib/libvcard.so.0 (0xb7965000) libkresources.so.1 => /opt/kde3/lib/libkresources.so.1 (0xb7942000) libkhtml.so.4 => /opt/kde3/lib/libkhtml.so.4 (0xb7578000) libkjs.so.1 => /opt/kde3/lib/libkjs.so.1 (0xb750d000) libpcreposix.so.0 => /usr/lib/libpcreposix.so.0 (0xb750a000) libkipi.so.2 => /home/daniel/digikam/progs/lib/libkipi.so.2 (0xb74d7000) libkutils.so.1 => /opt/kde3/lib/libkutils.so.1 (0xb7476000) libjasper.so.1 => /usr/lib/libjasper.so.1 (0xb7428000) libkexiv2.so.4 => /home/daniel/digikam/progs/lib/libkexiv2.so.4 (0xb7402000) libexiv2.so.2 => /home/daniel/digikam/progs/lib/libexiv2.so.2 (0xb7285000) libkdcraw.so.3 => /home/daniel/digikam/progs/lib/libkdcraw.so.3 (0xb726a000) libgpod.so.3 => /usr/lib/libgpod.so.3 (0xb721c000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7203000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb71fd000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb71c2000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7121000) libpcre.so.0 => /usr/lib/libpcre.so.0 (0xb70f6000) liblcms.so.1 => /usr/lib/liblcms.so.1 (0xb70c5000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb70a5000) libtiff.so.3 => /usr/lib/libtiff.so.3 (0xb7050000) libkdeprint.so.4 => /opt/kde3/lib/libkdeprint.so.4 (0xb6f86000) libkparts.so.2 => /opt/kde3/lib/libkparts.so.2 (0xb6f42000) libkio.so.4 => /opt/kde3/lib/libkio.so.4 (0xb6c0c000) libkdeui.so.4 => /opt/kde3/lib/libkdeui.so.4 (0xb6931000) libkdesu.so.4 => /opt/kde3/lib/libkdesu.so.4 (0xb691a000) libkwalletclient.so.1 => /opt/kde3/lib/libkwalletclient.so.1 (0xb6907000) libkdecore.so.4 => /opt/kde3/lib/libkdecore.so.4 (0xb66d3000) libDCOP.so.4 => /opt/kde3/lib/libDCOP.so.4 (0xb669f000) libresolv.so.2 => /lib/libresolv.so.2 (0xb668c000) libutil.so.1 => /lib/libutil.so.1 (0xb6688000) libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0xb6671000) libidn.so.11 => /usr/lib/libidn.so.11 (0xb663e000) libkdefx.so.4 => /opt/kde3/lib/libkdefx.so.4 (0xb6614000) libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0xb5f10000) libXi.so.6 => /usr/lib/libXi.so.6 (0xb5f07000) libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb5f00000) libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb5ef6000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb5eef000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb5eeb000) libXft.so.2 => /usr/lib/libXft.so.2 (0xb5ed8000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb5eac000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb5e3d000) libexpat.so.1 => /lib/libexpat.so.1 (0xb5e1c000) libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb5df6000) libXext.so.6 => /usr/lib/libXext.so.6 (0xb5de7000) libSM.so.6 => /usr/lib/libSM.so.6 (0xb5dde000) libICE.so.6 => /usr/lib/libICE.so.6 (0xb5dc5000) libpthread.so.0 => /lib/libpthread.so.0 (0xb5dae000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb5da5000) libX11.so.6 => /usr/lib/libX11.so.6 (0xb5c89000) libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xb5c86000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb5c6d000) libXau.so.6 => /usr/lib/libXau.so.6 (0xb5c69000) libfam.so.0 => /usr/lib/libfam.so.0 (0xb5c5f000) libacl.so.1 => /lib/libacl.so.1 (0xb5c57000) libattr.so.1 => /lib/libattr.so.1 (0xb5c50000) libz.so.1 => /lib/libz.so.1 (0xb5c3d000) libgphoto2.so.2 => /usr/lib/libgphoto2.so.2 (0xb5bc1000) libexif.so.12 => /usr/lib/libexif.so.12 (0xb5b95000) libgphoto2_port.so.0 => /usr/lib/libgphoto2_port.so.0 (0xb5b8c000) libltdl.so.3 => /usr/lib/libltdl.so.3 (0xb5b84000) libdl.so.2 => /lib/libdl.so.2 (0xb5b7f000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb5a91000) libm.so.6 => /lib/libm.so.6 (0xb5a6c000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb5a60000) libc.so.6 => /lib/libc.so.6 (0xb592d000) /lib/ld-linux.so.2 (0xb7f6a000) > Best, Arnd b.t.w: if I type these commands as root there is another output... regards, Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
Hi Daniel,
to make it short: I have no idea how to proceed, maybe someone else can help? (Still some comments/questions below...) On Sat, 23 Feb 2008, Daniel Bauer wrote: > On Saturday 23 February 2008 13.35:16, Arnd Baecker wrote: > > On Sat, 23 Feb 2008, Daniel Bauer wrote: > > > On Saturday 23 February 2008 10.33:18, Gilles Caulier wrote: > > > > Daniel, > > > > > > > > The crash is relevant of Exiv2 library. Which version you use ? > > > > > > > > Gilles > > > > > > Hello, good morning Gilles > > > > > > exiv2 -V gives: > > > exiv2 0.16 > > > > > > which exiv2 gives: > > > /usr/bin/exiv2 > > > > > > I compiled exiv2 with "./configure --prefix=/usr" (without prefix it > > > would have been installed in /usr/local/, which I thought was wrong...) > > > > Don't you install digikam & the rest to some other place? > > Yes, I use the script from digikam-page for local install in home directory, > with DIGIKAMDEST=/home/daniel/digikam/progs > > > I.e. the script compile_exiv2.sh > > at http://www.digikam.org/?q=download/svn > > puts stuff to DIGIKAMDEST > > (which I would recommend to be something accessible as > > user, and not root). > > Yes, I would use this as I did earlier, but dev.robotbattle.com/exiv2/trunk > still seems not to work... (sorry, forgot about that ...) > Now I copied the exiv2-0.16 folder (from the tar-file) to my home/digikam > directory and compiled again with prefix=/home/daniel/digikam/progs and run > make and make install as user. But digikam still crashed on opening the > editor. So I run the compile-digikam.sh again, but the crash still occurs... Very weird. Does this crash happen for a specific image, or for "all" images? (If it is a specific one, you could sent to me off-list). > The output of which exiv2 is now > /home/daniel/digikam/progs/bin/exiv2 > > > > What is the output of > > which digikam > > ldd `which digikam` > > ? > > I also have installed the stable digikam-Version from opensuse rpms. I always > had this, so in case of something not working in the svn version I could > still fall back to the stable one. This is the reason why I install svn in > the home directory as user... Yes, it is always good to have a fall-back. (However, I remember situations, where system installed versions caused problems in terms of library confusion, but this does not seem to be the case here, according to the output below) > Maybe you see this in the output of those > commands: > > daniel@venus:~> which digikam > /home/daniel/digikam/progs/bin/digikam > > daniel@venus:~> ldd `which digikam` > linux-gate.so.1 => (0xffffe000) > libdigikam.so.0 => /home/daniel/digikam/progs/lib/libdigikam.so.0 > (0xb7ac9000) > libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb7a39000) > libkabc.so.1 => /opt/kde3/lib/libkabc.so.1 (0xb798a000) > libvcard.so.0 => /opt/kde3/lib/libvcard.so.0 (0xb7965000) > libkresources.so.1 => /opt/kde3/lib/libkresources.so.1 (0xb7942000) > libkhtml.so.4 => /opt/kde3/lib/libkhtml.so.4 (0xb7578000) > libkjs.so.1 => /opt/kde3/lib/libkjs.so.1 (0xb750d000) > libpcreposix.so.0 => /usr/lib/libpcreposix.so.0 (0xb750a000) > libkipi.so.2 => /home/daniel/digikam/progs/lib/libkipi.so.2 > (0xb74d7000) > libkutils.so.1 => /opt/kde3/lib/libkutils.so.1 (0xb7476000) > libjasper.so.1 => /usr/lib/libjasper.so.1 (0xb7428000) > libkexiv2.so.4 => /home/daniel/digikam/progs/lib/libkexiv2.so.4 > (0xb7402000) > libexiv2.so.2 => /home/daniel/digikam/progs/lib/libexiv2.so.2 > (0xb7285000) > libkdcraw.so.3 => /home/daniel/digikam/progs/lib/libkdcraw.so.3 > (0xb726a000) > libgpod.so.3 => /usr/lib/libgpod.so.3 (0xb721c000) > libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7203000) > libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb71fd000) > libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb71c2000) > libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7121000) > libpcre.so.0 => /usr/lib/libpcre.so.0 (0xb70f6000) > liblcms.so.1 => /usr/lib/liblcms.so.1 (0xb70c5000) > libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb70a5000) > libtiff.so.3 => /usr/lib/libtiff.so.3 (0xb7050000) > libkdeprint.so.4 => /opt/kde3/lib/libkdeprint.so.4 (0xb6f86000) > libkparts.so.2 => /opt/kde3/lib/libkparts.so.2 (0xb6f42000) > libkio.so.4 => /opt/kde3/lib/libkio.so.4 (0xb6c0c000) > libkdeui.so.4 => /opt/kde3/lib/libkdeui.so.4 (0xb6931000) > libkdesu.so.4 => /opt/kde3/lib/libkdesu.so.4 (0xb691a000) > libkwalletclient.so.1 => /opt/kde3/lib/libkwalletclient.so.1 > (0xb6907000) > libkdecore.so.4 => /opt/kde3/lib/libkdecore.so.4 (0xb66d3000) > libDCOP.so.4 => /opt/kde3/lib/libDCOP.so.4 (0xb669f000) > libresolv.so.2 => /lib/libresolv.so.2 (0xb668c000) > libutil.so.1 => /lib/libutil.so.1 (0xb6688000) > libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0xb6671000) > libidn.so.11 => /usr/lib/libidn.so.11 (0xb663e000) > libkdefx.so.4 => /opt/kde3/lib/libkdefx.so.4 (0xb6614000) > libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0xb5f10000) > libXi.so.6 => /usr/lib/libXi.so.6 (0xb5f07000) > libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb5f00000) > libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb5ef6000) > libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb5eef000) > libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb5eeb000) > libXft.so.2 => /usr/lib/libXft.so.2 (0xb5ed8000) > libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb5eac000) > libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb5e3d000) > libexpat.so.1 => /lib/libexpat.so.1 (0xb5e1c000) > libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb5df6000) > libXext.so.6 => /usr/lib/libXext.so.6 (0xb5de7000) > libSM.so.6 => /usr/lib/libSM.so.6 (0xb5dde000) > libICE.so.6 => /usr/lib/libICE.so.6 (0xb5dc5000) > libpthread.so.0 => /lib/libpthread.so.0 (0xb5dae000) > libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb5da5000) > libX11.so.6 => /usr/lib/libX11.so.6 (0xb5c89000) > libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xb5c86000) > libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb5c6d000) > libXau.so.6 => /usr/lib/libXau.so.6 (0xb5c69000) > libfam.so.0 => /usr/lib/libfam.so.0 (0xb5c5f000) > libacl.so.1 => /lib/libacl.so.1 (0xb5c57000) > libattr.so.1 => /lib/libattr.so.1 (0xb5c50000) > libz.so.1 => /lib/libz.so.1 (0xb5c3d000) > libgphoto2.so.2 => /usr/lib/libgphoto2.so.2 (0xb5bc1000) > libexif.so.12 => /usr/lib/libexif.so.12 (0xb5b95000) > libgphoto2_port.so.0 => /usr/lib/libgphoto2_port.so.0 (0xb5b8c000) > libltdl.so.3 => /usr/lib/libltdl.so.3 (0xb5b84000) > libdl.so.2 => /lib/libdl.so.2 (0xb5b7f000) > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb5a91000) > libm.so.6 => /lib/libm.so.6 (0xb5a6c000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb5a60000) > libc.so.6 => /lib/libc.so.6 (0xb592d000) > /lib/ld-linux.so.2 (0xb7f6a000) So to me all looks fine and like on my system (Only difference: I currently have exiv2 0.16-pre1...) > > Best, Arnd > > b.t.w: if I type these commands as root there is another output... Presumably some paths are set differently? (I.e. To do it really correctly, one has to use the lines from start_digikam.sh and paste them into a shell window and then do the ldd. I think it then should give the same output, both as normal user and root; however these linking issues always confuse me ... So to summarize: I have no clue about what is going on, sorry! Anyone else having any ideas?? Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
Hi Arnd,
It's not the first time I produce "special" problems... I don't know if it's me or my computer. For my mental health sake I hope it's my computer :-) I added some comments more below... On Saturday 23 February 2008 16.51:11, Arnd Baecker wrote: > Hi Daniel, > > to make it short: I have no idea how to proceed, > maybe someone else can help? > (Still some comments/questions below...) > > On Sat, 23 Feb 2008, Daniel Bauer wrote: > > On Saturday 23 February 2008 13.35:16, Arnd Baecker wrote: > > > On Sat, 23 Feb 2008, Daniel Bauer wrote: > > > > On Saturday 23 February 2008 10.33:18, Gilles Caulier wrote: > > > > > Daniel, > > > > > > > > > > The crash is relevant of Exiv2 library. Which version you use ? > > > > > > > > > > Gilles > > > > > > > > Hello, good morning Gilles > > > > > > > > exiv2 -V gives: > > > > exiv2 0.16 > > > > > > > > which exiv2 gives: > > > > /usr/bin/exiv2 > > > > > > > > I compiled exiv2 with "./configure --prefix=/usr" (without prefix it > > > > would have been installed in /usr/local/, which I thought was > > > > wrong...) > > > > > > Don't you install digikam & the rest to some other place? > > > > Yes, I use the script from digikam-page for local install in home > > directory, with DIGIKAMDEST=/home/daniel/digikam/progs > > > > > I.e. the script compile_exiv2.sh > > > at http://www.digikam.org/?q=download/svn > > > puts stuff to DIGIKAMDEST > > > (which I would recommend to be something accessible as > > > user, and not root). > > > > Yes, I would use this as I did earlier, but > > dev.robotbattle.com/exiv2/trunk still seems not to work... > > (sorry, forgot about that ...) > > > Now I copied the exiv2-0.16 folder (from the tar-file) to my home/digikam > > directory and compiled again with prefix=/home/daniel/digikam/progs and > > run make and make install as user. But digikam still crashed on opening > > the editor. So I run the compile-digikam.sh again, but the crash still > > occurs... > > Very weird. Does this crash happen for a specific image, > or for "all" images? > (If it is a specific one, you could sent to me off-list). It seems to happen with all images. I tried only jpg's though. > > > The output of which exiv2 is now > > /home/daniel/digikam/progs/bin/exiv2 > > > > > What is the output of > > > which digikam > > > ldd `which digikam` > > > ? > > > > I also have installed the stable digikam-Version from opensuse rpms. I > > always had this, so in case of something not working in the svn version I > > could still fall back to the stable one. This is the reason why I install > > svn in the home directory as user... > > Yes, it is always good to have a fall-back. > (However, I remember situations, where system installed > versions caused problems in terms of library confusion, but > this does not seem to be the case here, according to the output below) I don't know. I remembered my Windows from earlier bad times and so I tried a reboot :-) Interesting is, that when I now type which digikam I get: /opt/kde3/bin/digikam and for which exiv2 I get: /usr/bin/exiv2 Maybe the compilation I did before I entered these command the last time changed something, which is now in "normal" order again? I get the above results also after running the start-digikam.sh script with all those export stuff... > > Maybe you see this in the output of those > > commands: > > > > daniel@venus:~> which digikam > > /home/daniel/digikam/progs/bin/digikam > > > > daniel@venus:~> ldd `which digikam` > > linux-gate.so.1 => (0xffffe000) > > libdigikam.so.0 => /home/daniel/digikam/progs/lib/libdigikam.so.0 > > (0xb7ac9000) > > libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb7a39000) > > libkabc.so.1 => /opt/kde3/lib/libkabc.so.1 (0xb798a000) > > libvcard.so.0 => /opt/kde3/lib/libvcard.so.0 (0xb7965000) > > libkresources.so.1 => /opt/kde3/lib/libkresources.so.1 > > (0xb7942000) libkhtml.so.4 => /opt/kde3/lib/libkhtml.so.4 (0xb7578000) > > libkjs.so.1 => /opt/kde3/lib/libkjs.so.1 (0xb750d000) > > libpcreposix.so.0 => /usr/lib/libpcreposix.so.0 (0xb750a000) > > libkipi.so.2 => /home/daniel/digikam/progs/lib/libkipi.so.2 > > (0xb74d7000) > > libkutils.so.1 => /opt/kde3/lib/libkutils.so.1 (0xb7476000) > > libjasper.so.1 => /usr/lib/libjasper.so.1 (0xb7428000) > > libkexiv2.so.4 => /home/daniel/digikam/progs/lib/libkexiv2.so.4 > > (0xb7402000) > > libexiv2.so.2 => /home/daniel/digikam/progs/lib/libexiv2.so.2 > > (0xb7285000) > > libkdcraw.so.3 => /home/daniel/digikam/progs/lib/libkdcraw.so.3 > > (0xb726a000) > > libgpod.so.3 => /usr/lib/libgpod.so.3 (0xb721c000) > > libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 > > (0xb7203000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 > > (0xb71fd000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 > > (0xb71c2000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7121000) > > libpcre.so.0 => /usr/lib/libpcre.so.0 (0xb70f6000) > > liblcms.so.1 => /usr/lib/liblcms.so.1 (0xb70c5000) > > libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb70a5000) > > libtiff.so.3 => /usr/lib/libtiff.so.3 (0xb7050000) > > libkdeprint.so.4 => /opt/kde3/lib/libkdeprint.so.4 (0xb6f86000) > > libkparts.so.2 => /opt/kde3/lib/libkparts.so.2 (0xb6f42000) > > libkio.so.4 => /opt/kde3/lib/libkio.so.4 (0xb6c0c000) > > libkdeui.so.4 => /opt/kde3/lib/libkdeui.so.4 (0xb6931000) > > libkdesu.so.4 => /opt/kde3/lib/libkdesu.so.4 (0xb691a000) > > libkwalletclient.so.1 => /opt/kde3/lib/libkwalletclient.so.1 > > (0xb6907000) > > libkdecore.so.4 => /opt/kde3/lib/libkdecore.so.4 (0xb66d3000) > > libDCOP.so.4 => /opt/kde3/lib/libDCOP.so.4 (0xb669f000) > > libresolv.so.2 => /lib/libresolv.so.2 (0xb668c000) > > libutil.so.1 => /lib/libutil.so.1 (0xb6688000) > > libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0xb6671000) > > libidn.so.11 => /usr/lib/libidn.so.11 (0xb663e000) > > libkdefx.so.4 => /opt/kde3/lib/libkdefx.so.4 (0xb6614000) > > libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0xb5f10000) > > libXi.so.6 => /usr/lib/libXi.so.6 (0xb5f07000) > > libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb5f00000) > > libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb5ef6000) > > libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb5eef000) > > libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb5eeb000) > > libXft.so.2 => /usr/lib/libXft.so.2 (0xb5ed8000) > > libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb5eac000) > > libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb5e3d000) > > libexpat.so.1 => /lib/libexpat.so.1 (0xb5e1c000) > > libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb5df6000) > > libXext.so.6 => /usr/lib/libXext.so.6 (0xb5de7000) > > libSM.so.6 => /usr/lib/libSM.so.6 (0xb5dde000) > > libICE.so.6 => /usr/lib/libICE.so.6 (0xb5dc5000) > > libpthread.so.0 => /lib/libpthread.so.0 (0xb5dae000) > > libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb5da5000) > > libX11.so.6 => /usr/lib/libX11.so.6 (0xb5c89000) > > libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xb5c86000) > > libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb5c6d000) > > libXau.so.6 => /usr/lib/libXau.so.6 (0xb5c69000) > > libfam.so.0 => /usr/lib/libfam.so.0 (0xb5c5f000) > > libacl.so.1 => /lib/libacl.so.1 (0xb5c57000) > > libattr.so.1 => /lib/libattr.so.1 (0xb5c50000) > > libz.so.1 => /lib/libz.so.1 (0xb5c3d000) > > libgphoto2.so.2 => /usr/lib/libgphoto2.so.2 (0xb5bc1000) > > libexif.so.12 => /usr/lib/libexif.so.12 (0xb5b95000) > > libgphoto2_port.so.0 => /usr/lib/libgphoto2_port.so.0 > > (0xb5b8c000) libltdl.so.3 => /usr/lib/libltdl.so.3 (0xb5b84000) > > libdl.so.2 => /lib/libdl.so.2 (0xb5b7f000) > > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb5a91000) > > libm.so.6 => /lib/libm.so.6 (0xb5a6c000) > > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb5a60000) > > libc.so.6 => /lib/libc.so.6 (0xb592d000) > > /lib/ld-linux.so.2 (0xb7f6a000) > > So to me all looks fine and like on my system > (Only difference: I currently have exiv2 0.16-pre1...) > > > > Best, Arnd > > > > b.t.w: if I type these commands as root there is another output... > > Presumably some paths are set differently? > (I.e. To do it really correctly, one has to use the lines > from start_digikam.sh and paste them into a shell window > and then do the ldd. I think it then should give > the same output, both as normal user and root; however > these linking issues always confuse me ... > > So to summarize: I have no clue about what is going on, sorry! > > Anyone else having any ideas?? > > Best, Arnd In my backup from my earlier install on the last system I see that I the last command (the line after hash -r) in my old start-digikam.sh was: digikam --caption digikam9 --config digikam9svnrc while now it is only "digikam" (because I freshly downloaded it from digikam.org). Out of couriosity I tried to add this caption...etc. Then at start-u digikam again asked me where the album is, and after displaying the Startpage in already crahed when I wanted to open an album (click on an album in the left bar). When I remove this again, it starts up normal and crashes when opening the editor, no matter whether I open the editor via Menu, via context-Menu or by telling the settings to always open the editor. Is there a possibility to add a command somewhere to the compile-script to get more detailed output from the crash (like debug or something)? I could then delete everything, begin from the beginning again and maybe deliver more info? Don't know... kind regards Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
On Sat, 23 Feb 2008, Daniel Bauer wrote:
> Hi Arnd, > > It's not the first time I produce "special" problems... I don't know if it's > me or my computer. For my mental health sake I hope it's my computer :-) Surely the computer! [...] > I don't know. I remembered my Windows from earlier bad times and so I tried a > reboot :-) Uff, obviously you are getting desparate ... ;-) > Interesting is, that when I now type which digikam I get: > /opt/kde3/bin/digikam > > and for which exiv2 I get: > /usr/bin/exiv2 > > Maybe the compilation I did before I entered these command the last time > changed something, which is now in "normal" order again? > > I get the above results also after running the start-digikam.sh script with > all those export stuff... These "export"s only work "locally", i.e. within the script. The script cannot/does not change anything outside of itself. Only if you copy and paste the commands of the script to your konsole (shell), they become active/visble. [...] > In my backup from my earlier install on the last system I see that I the last > command (the line after hash -r) in my old start-digikam.sh was: > > digikam --caption digikam9 --config digikam9svnrc > > while now it is only "digikam" (because I freshly downloaded it from > digikam.org). > > Out of couriosity I tried to add this caption...etc. Then at start-u digikam > again asked me where the album is, and after displaying the Startpage in > already crahed when I wanted to open an album (click on an album in the left > bar). > > When I remove this again, it starts up normal and crashes when opening the > editor, no matter whether I open the editor via Menu, via context-Menu or by > telling the settings to always open the editor. > > Is there a possibility to add a command somewhere to the compile-script to get > more detailed output from the crash (like debug or something)? I could then > delete everything, begin from the beginning again and maybe deliver more > info? Don't know... Yes, that might be worth a try. Acually, maybe you should even (temporarily) remove digikam, libkdcraw, libkexiv2, libkipi, kipi-plugins, exiv2 from your system (libjasper is ok), to be sure that there is no library mess-up. To obtain debuggin information, you have to modify the configure command in all scripts to ./configure --enable-debug=full HERE_THE_NORMAL_OPTIONS To obtain a backtrace you have to # gdb digikam > run > ... > _crash here_ > ... > bt > _the backtrace is here_ > quit (A lot more about backtraces/crash reports is discussed http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports here, but this just for reference, don't think you need to read that ;-). Hopefully this will help to figure out what is going wrong ... Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
ok, I'll give it a try tomorrow...
have a nice evening :-) Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Arnd Baecker
Hello,
I have a working install now (not tested a lot though...) On Saturday 23 February 2008 19.13:16, Arnd Baecker wrote: > [...] > Yes, that might be worth a try. > Acually, maybe you should even (temporarily) remove > digikam, libkdcraw, libkexiv2, libkipi, kipi-plugins, exiv2 > from your system (libjasper is ok), > to be sure that there is no library mess-up. So, here's what I found out: After deinstalling all of the above the program run without crashing (without a previous fresh compile). So I installed one after the other again and everything went fine untill I installed the kdegraphics3 package ("Base Libraries for KDE graphics applications". Having that installed digikam crashed. I tried several times to install and uninstall kdegraphics3 and it is clearly reproducible: when it's installed, digikam crashes, when it's removed, digikam works. I have installed all other things again (digikam, libkdcraw, libkexiv2, libkipi, kipi-plugins, exiv2), even kdegraphics3-imaging (because I like kuickshow) - and it still works. It's just the kdegraphics3 basic package that causes the crash. > > To obtain debuggin information, you have to modify the configure command > in all scripts to > ./configure --enable-debug=full HERE_THE_NORMAL_OPTIONS > > To obtain a backtrace you have to > # gdb digikam > > > run > > ... > > _crash here_ > > ... > > bt > > _the backtrace is here_ > > quit I did that, but I think there is not a lot of info. Would I have to delete all the svn-stuff before compiling it with the debug option? (I just run the modified compile-digikam.sh with the --enable-debug=full added to the two configure lines without deleting anything first). If it is necessary to first delete everything to find out more, tell me, and I'll do it. Well here's what came out (kdegraphics3 installed, the crash now already occured when trying to display the album previews, directly after starting): daniel@venus:~/digikam/source> which digikam /home/daniel/digikam/progs/bin/digikam daniel@venus:~/digikam/source> gdb digikam GNU gdb 6.6.50.20070726-cvs Copyright (C) 2007 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 "i586-suse-linux"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /home/daniel/digikam/progs/bin/digikam [Thread debugging using libthread_db enabled] [New Thread 0xb597f6d0 (LWP 16507)] [New Thread 0xb569eb90 (LWP 16510)] [Thread 0xb569eb90 (LWP 16510) exited] [New Thread 0xb4e9db90 (LWP 16511)] [Thread 0xb4e9db90 (LWP 16511) exited] Found dcraw version: 8.82 terminate called after throwing an instance of 'Exiv2::Error' what(): Die Rgistrierung für das HerstellerfeldInfo ist voll Program received signal SIGABRT, Aborted. [Switching to Thread 0xb597f6d0 (LWP 16507)] 0xffffe410 in __kernel_vsyscall () (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb59ad8f5 in raise () from /lib/libc.so.6 #2 0xb59af1e1 in abort () from /lib/libc.so.6 #3 0xb5ba4380 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #4 0xb5ba1c25 in ?? () from /usr/lib/libstdc++.so.6 #5 0xb5ba1c62 in std::terminate () from /usr/lib/libstdc++.so.6 #6 0xb5ba1d8a in __cxa_throw () from /usr/lib/libstdc++.so.6 #7 0xb739da09 in Exiv2::ExifTags::registerMakerTagInfo () from /home/daniel/digikam/progs/lib/libexiv2.so.2 #8 0xb7395a5b in Exiv2::SonyMakerNote::RegisterMn::RegisterMn () from /home/daniel/digikam/progs/lib/libexiv2.so.2 #9 0xb2e5c5cf in ?? () from /usr/lib/libexiv2.so.0 #10 0xb2e7a1a5 in ?? () from /usr/lib/libexiv2.so.0 #11 0xb2eb0ff4 in ?? () from /usr/lib/libexiv2.so.0 #12 0x089ee7d0 in ?? () #13 0xbff59778 in ?? () #14 0xb2df2198 in _init () from /usr/lib/libexiv2.so.0 Backtrace stopped: frame did not save the PC (gdb) ----------------------- now: better go out and enjoy the beautiful spring weather this sunday :-) kind regards Daniel Oh: it would be helpful if it was possible to have it running with kdegraphics3 installed because of the ksnapshot tool which is in there - I used this quite often... -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
Arnd,
I recommend you to ping Andreas (Exiv2 author) about this thread He is not registered to digikam-users ml (only on devel one...) Gilles 2008/2/24, Daniel Bauer <[hidden email]>: Hello, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Daniel Bauer-2
> So, here's what I found out:
> > After deinstalling all of the above the program run without crashing > (without a previous fresh compile). So I installed one after the other > again and everything went fine untill I installed the kdegraphics3 package > ("Base Libraries for KDE graphics applications". Having that installed > digikam crashed. > > I tried several times to install and uninstall kdegraphics3 and it is > clearly reproducible: when it's installed, digikam crashes, when it's > removed, digikam works. > #2 0xb59af1e1 in abort () from /lib/libc.so.6 > #3 0xb5ba4380 in __gnu_cxx::__verbose_terminate_handler () > from /usr/lib/libstdc++.so.6 > #4 0xb5ba1c25 in ?? () from /usr/lib/libstdc++.so.6 > #5 0xb5ba1c62 in std::terminate () from /usr/lib/libstdc++.so.6 > #6 0xb5ba1d8a in __cxa_throw () from /usr/lib/libstdc++.so.6 > #7 0xb739da09 in Exiv2::ExifTags::registerMakerTagInfo () > from /home/daniel/digikam/progs/lib/libexiv2.so.2 > #8 0xb7395a5b in Exiv2::SonyMakerNote::RegisterMn::RegisterMn () > from /home/daniel/digikam/progs/lib/libexiv2.so.2 I have seen this crash some time ago. The cause was a messup of exiv2 and/or libkexiv2 and/or digikam, I do not remember. When installation of kdegraphics3 triggers your problem, then likely something gets installed (libkexiv2? Plugins?) that is then used with binaries that were compiled against another version of exiv2. It must be something related to your setup in the home directory. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
On Sunday 24 February 2008 23.00:40, Marcel Wiesweg wrote:
> I have seen this crash some time ago. The cause was a messup of exiv2 > and/or libkexiv2 and/or digikam, I do not remember. > When installation of kdegraphics3 triggers your problem, then likely > something gets installed (libkexiv2? Plugins?) that is then used with > binaries that were compiled against another version of exiv2. It must be > something related to your setup in the home directory. Hello, And how can I find out whats wrong in my setup? libkexiv2-3 is installed, but i doesn't make a change whether it is or not (it doesn't disturb svn digikam). It's just kdegraphics3 that makes the difference. It installs the following files: /opt/kde3/bin/ksnapshot /opt/kde3/bin/kviewshell /opt/kde3/bin/printnodetest /opt/kde3/bin/svgdisplay /opt/kde3/bin/xf86gammacfg /opt/kde3/lib/kde3/djvuviewpart.la /opt/kde3/lib/kde3/djvuviewpart.so /opt/kde3/lib/kde3/emptymultipagepart.la /opt/kde3/lib/kde3/emptymultipagepart.so /opt/kde3/lib/kde3/gsthumbnail.la /opt/kde3/lib/kde3/gsthumbnail.so /opt/kde3/lib/kde3/kcm_kgamma.la /opt/kde3/lib/kde3/kcm_kgamma.so /opt/kde3/lib/kde3/kfile_bmp.la /opt/kde3/lib/kde3/kfile_bmp.so /opt/kde3/lib/kde3/kfile_dds.la /opt/kde3/lib/kde3/kfile_dds.so /opt/kde3/lib/kde3/kfile_dvi.la /opt/kde3/lib/kde3/kfile_dvi.so /opt/kde3/lib/kde3/kfile_exr.la /opt/kde3/lib/kde3/kfile_exr.so /opt/kde3/lib/kde3/kfile_gif.la /opt/kde3/lib/kde3/kfile_gif.so /opt/kde3/lib/kde3/kfile_ico.la /opt/kde3/lib/kde3/kfile_ico.so /opt/kde3/lib/kde3/kfile_jpeg.la /opt/kde3/lib/kde3/kfile_jpeg.so /opt/kde3/lib/kde3/kfile_pcx.la /opt/kde3/lib/kde3/kfile_pcx.so /opt/kde3/lib/kde3/kfile_pdf.la /opt/kde3/lib/kde3/kfile_pdf.so /opt/kde3/lib/kde3/kfile_png.la /opt/kde3/lib/kde3/kfile_png.so /opt/kde3/lib/kde3/kfile_pnm.la /opt/kde3/lib/kde3/kfile_pnm.so /opt/kde3/lib/kde3/kfile_ps.la /opt/kde3/lib/kde3/kfile_ps.so /opt/kde3/lib/kde3/kfile_raw.la /opt/kde3/lib/kde3/kfile_raw.so /opt/kde3/lib/kde3/kfile_rgb.la /opt/kde3/lib/kde3/kfile_rgb.so /opt/kde3/lib/kde3/kfile_tga.la /opt/kde3/lib/kde3/kfile_tga.so /opt/kde3/lib/kde3/kfile_tiff.la /opt/kde3/lib/kde3/kfile_tiff.so /opt/kde3/lib/kde3/kfile_xbm.la /opt/kde3/lib/kde3/kfile_xbm.so /opt/kde3/lib/kde3/kfile_xpm.la /opt/kde3/lib/kde3/kfile_xpm.so /opt/kde3/lib/kde3/kviewerpart.la /opt/kde3/lib/kde3/kviewerpart.so /opt/kde3/lib/kde3/libdjvu.la /opt/kde3/lib/kde3/libdjvu.so /opt/kde3/lib/kde3/libksvgplugin.la /opt/kde3/lib/kde3/libksvgplugin.so /opt/kde3/lib/kde3/libksvgrendererlibart.la /opt/kde3/lib/kde3/libksvgrendererlibart.so /opt/kde3/lib/kde3/svgthumbnail.la /opt/kde3/lib/kde3/svgthumbnail.so /opt/kde3/lib/libkmultipage.la /opt/kde3/lib/libkmultipage.so /opt/kde3/lib/libkmultipage.so.0 /opt/kde3/lib/libkmultipage.so.0.0.0 /opt/kde3/lib/libksvg.la /opt/kde3/lib/libksvg.so /opt/kde3/lib/libksvg.so.0 /opt/kde3/lib/libksvg.so.0.0.1 /opt/kde3/lib/libtext2path.la /opt/kde3/lib/libtext2path.so /opt/kde3/lib/libtext2path.so.0 /opt/kde3/lib/libtext2path.so.0.0.0 /opt/kde3/share/applications/kde/ksnapshot.desktop /opt/kde3/share/applnk/.hidden /opt/kde3/share/applnk/.hidden/kgamma.desktop /opt/kde3/share/apps/djvumultipage.rc /opt/kde3/share/apps/kgamma /opt/kde3/share/apps/kgamma/pics /opt/kde3/share/apps/kgamma/pics/background.png /opt/kde3/share/apps/kgamma/pics/cmyscale.png /opt/kde3/share/apps/kgamma/pics/darkgrey.png /opt/kde3/share/apps/kgamma/pics/greyscale.png /opt/kde3/share/apps/kgamma/pics/lightgrey.png /opt/kde3/share/apps/kgamma/pics/midgrey.png /opt/kde3/share/apps/kgamma/pics/rgbscale.png /opt/kde3/share/apps/ksvg /opt/kde3/share/apps/ksvg/ksvgplugin.rc /opt/kde3/share/apps/kviewerpart /opt/kde3/share/apps/kviewerpart/icons /opt/kde3/share/apps/kviewerpart/icons/hicolor /opt/kde3/share/apps/kviewerpart/icons/hicolor/16x16 /opt/kde3/share/apps/kviewerpart/icons/hicolor/16x16/actions /opt/kde3/share/apps/kviewerpart/icons/hicolor/16x16/actions/movetool.png /opt/kde3/share/apps/kviewerpart/icons/hicolor/16x16/actions/selectiontool.png /opt/kde3/share/apps/kviewerpart/icons/hicolor/22x22 /opt/kde3/share/apps/kviewerpart/icons/hicolor/22x22/actions /opt/kde3/share/apps/kviewerpart/icons/hicolor/22x22/actions/movetool.png /opt/kde3/share/apps/kviewerpart/icons/hicolor/22x22/actions/selectiontool.png /opt/kde3/share/apps/kviewerpart/icons/hicolor/32x32 /opt/kde3/share/apps/kviewerpart/icons/hicolor/32x32/actions /opt/kde3/share/apps/kviewerpart/icons/hicolor/32x32/actions/movetool.png /opt/kde3/share/apps/kviewerpart/icons/hicolor/48x48 /opt/kde3/share/apps/kviewerpart/icons/hicolor/48x48/actions /opt/kde3/share/apps/kviewerpart/icons/hicolor/48x48/actions/movetool.png /opt/kde3/share/apps/kviewerpart/kviewerpart.rc /opt/kde3/share/apps/kviewshell /opt/kde3/share/apps/kviewshell/kviewshell.rc /opt/kde3/share/apps/kviewviewer /opt/kde3/share/apps/kviewviewer/kpartplugins /opt/kde3/share/apps/kviewviewer/kpartplugins/kviewbrowser.desktop /opt/kde3/share/apps/kviewviewer/kpartplugins/kviewbrowser.rc /opt/kde3/share/apps/kviewviewer/kviewpopup.rc /opt/kde3/share/apps/kviewviewer/kviewviewer.rc /opt/kde3/share/apps/kviewviewer/kviewviewer_ro.rc /opt/kde3/share/config.kcfg/djvumultipage.kcfg /opt/kde3/share/config.kcfg/kviewshell.kcfg /opt/kde3/share/doc/HTML/en/kgamma /opt/kde3/share/doc/HTML/en/kgamma/common /opt/kde3/share/doc/HTML/en/kgamma/index.cache.bz2 /opt/kde3/share/doc/HTML/en/kgamma/index.docbook /opt/kde3/share/doc/HTML/en/ksnapshot /opt/kde3/share/doc/HTML/en/ksnapshot/common /opt/kde3/share/doc/HTML/en/ksnapshot/index.cache.bz2 /opt/kde3/share/doc/HTML/en/ksnapshot/index.docbook /opt/kde3/share/doc/HTML/en/ksnapshot/preview.png /opt/kde3/share/doc/HTML/en/ksnapshot/window.png /opt/kde3/share/icons/hicolor/16x16 /opt/kde3/share/icons/hicolor/16x16/apps /opt/kde3/share/icons/hicolor/16x16/apps/kgamma.png /opt/kde3/share/icons/hicolor/16x16/apps/ksnapshot.png /opt/kde3/share/icons/hicolor/16x16/apps/kviewshell.png /opt/kde3/share/icons/hicolor/22x22/apps/ksnapshot.png /opt/kde3/share/icons/hicolor/32x32 /opt/kde3/share/icons/hicolor/32x32/apps /opt/kde3/share/icons/hicolor/32x32/apps/kgamma.png /opt/kde3/share/icons/hicolor/32x32/apps/ksnapshot.png /opt/kde3/share/icons/hicolor/32x32/apps/kviewshell.png /opt/kde3/share/icons/hicolor/48x48 /opt/kde3/share/icons/hicolor/48x48/apps /opt/kde3/share/icons/hicolor/48x48/apps/kgamma.png /opt/kde3/share/icons/hicolor/48x48/apps/ksnapshot.png /opt/kde3/share/icons/hicolor/48x48/apps/kviewshell.png /opt/kde3/share/icons/hicolor/scalable/apps/ksnapshot.svgz /opt/kde3/share/services/djvumultipage.desktop /opt/kde3/share/services/emptymultipage.desktop /opt/kde3/share/services/gsthumbnail.desktop /opt/kde3/share/services/kfile_bmp.desktop /opt/kde3/share/services/kfile_dds.desktop /opt/kde3/share/services/kfile_dvi.desktop /opt/kde3/share/services/kfile_exr.desktop /opt/kde3/share/services/kfile_gif.desktop /opt/kde3/share/services/kfile_ico.desktop /opt/kde3/share/services/kfile_jpeg.desktop /opt/kde3/share/services/kfile_pcx.desktop /opt/kde3/share/services/kfile_pdf.desktop /opt/kde3/share/services/kfile_png.desktop /opt/kde3/share/services/kfile_pnm.desktop /opt/kde3/share/services/kfile_ps.desktop /opt/kde3/share/services/kfile_raw.desktop /opt/kde3/share/services/kfile_rgb.desktop /opt/kde3/share/services/kfile_tga.desktop /opt/kde3/share/services/kfile_tiff.desktop /opt/kde3/share/services/kfile_xbm.desktop /opt/kde3/share/services/kfile_xpm.desktop /opt/kde3/share/services/ksvglibartcanvas.desktop /opt/kde3/share/services/ksvgplugin.desktop /opt/kde3/share/services/svgthumbnail.desktop /opt/kde3/share/servicetypes/kmultipage.desktop /opt/kde3/share/servicetypes/ksvgrenderer.desktop kind regards Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Marcel Wiesweg
On Sunday 24 February 2008 23.00:40, Marcel Wiesweg wrote:
> [...] > It must be > something related to your setup in the home directory. So to have a clean home directory I created a new user, but its the same here... what I did: - create new user "dkam" - log into this user with kde - created /home/dkam/digikam/source - copied exiv2-0.16.tar.gz to /home/dkam/digikam, unpacked here - cd /home/dkam/digikam/exiv2-0.16 - ./configure prefix=/home/dkam/digikam/progs - make - make install - cd /home/dkam/digikam/source - ./compile_digikam.sh (script as from digikam site, but with added "--enable-debug=full" to the two configure lines) - cd /home/dkam/digikam/ - ./start_digikam.sh - everything ok - installed kdegraphics3 with Yast (Suse install tool) - ./start_digikam.sh - crashed (same bt results as in other install) - removed kdegraphics3 with Yast - ./start_digikam.sh - everything ok again So, it seems it is nothing wrong in my normal home directory "daniel", or my openSuse 10.3 makes something wrong in every users home directory? kind regards Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Marcel Wiesweg
So, something more I found out...:
kdegraphics3 depends on libexiv2. If I just install libexiv2 (without kdegraphics3) svn digikam runs. If I install kdegraphics3 digikam crashes. Now I de-install libexiv2 but leaving kde3graphics installed (ignoring dependencies), digikam runs... So, it is a game between kdegraphics3 and libexiv2 that makes digikam crash. Each of the libraries alone is ok, but together not... Next I installed exiv2-0.16 from tar into /usr. That doesn't disturb digikam. But now konqueror, gwenview etc. are missing libexiv2.so.0, because I now have libexiv2.so.2. So I guess I'll have to uninstall exiv2-0.16 and reinstall suse's libexiv2 0.15-8.2 again, which will crash digikam but leave me a running system... Anyway I wonder why the svn installed in home looks after /usr/lib/libexiv2.so.0 (as in the backtrace of the crash)... kind regards Daniel _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
Op maandag 25 februari 2008, schreef Daniel Bauer:
> Next I installed exiv2-0.16 from tar into /usr. That doesn't > disturb digikam. But now konqueror, gwenview etc. are missing > libexiv2.so.0, because I now have libexiv2.so.2. This is exactly what I was meaning to write to you. This fact made me stop using the svn-version of exiv2 in my script. > > So I guess I'll have to uninstall exiv2-0.16 and reinstall suse's > libexiv2 0.15-8.2 again, which will crash digikam but leave me a > running system... Indeed that is what I did, but my install of digikam runs smoothly. Currently 0.9.4svn compiled from serial 777831. The difference is that I compile and install in standard /opt/kde3. I once tried to compile and install in my homedir but that totally failed. I didn't bother to get that working, in the knowledge that a standard-install works flawless for me. > > Anyway I wonder why the svn installed in home looks > after /usr/lib/libexiv2.so.0 (as in the backtrace of the crash)... I don't know about this, but it looks like a version mixup to me. Probably the old 0.15 libexiv2 was installed together with kdegraphics, and used to compile digikam against. If subsequently digikam uses 0.16 functions (don't ask me how this can happen) then I can imagine that it crashes. Now you have uninstalled 0.16 and installed 0.15-8.2, I suggest you try to recompile digikam-libs and digikam manually in your homedir. If this doesn't work, then maybe my way is an option for you. Hope you will succeed and get digikam working, because there is no photograpic life without it under linux... ;-) Caspar. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Daniel Bauer-2
> So, something more I found out...:
> > kdegraphics3 depends on libexiv2. If I just install libexiv2 (without > kdegraphics3) svn digikam runs. If I install kdegraphics3 digikam crashes. > > Now I de-install libexiv2 but leaving kde3graphics installed (ignoring > dependencies), digikam runs... > > So, it is a game between kdegraphics3 and libexiv2 that makes digikam > crash. Each of the libraries alone is ok, but together not... > > Next I installed exiv2-0.16 from tar into /usr. That doesn't disturb > digikam. But now konqueror, gwenview etc. are missing libexiv2.so.0, > because I now have libexiv2.so.2. > > So I guess I'll have to uninstall exiv2-0.16 and reinstall suse's libexiv2 > 0.15-8.2 again, which will crash digikam but leave me a running system... That's exactly the kind of version mixup of libexiv2. Some KDE libs load libexiv2.so.0, and digikam is compiled against libexiv2.so.2. It crashes when loading so.0. For some reason the libs are binary incompatible, but the linker does not notice. Why this is the case I leave to others to comment (that means, I dont know). > > Anyway I wonder why the svn installed in home looks > after /usr/lib/libexiv2.so.0 (as in the backtrace of the crash)... > > kind regards > > Daniel _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
Hi Caspar,
On Monday 25 February 2008 19.28:01, Caspar Maessen wrote: > [...] > I don't know about this, but it looks like a version mixup to me. > Probably the old 0.15 libexiv2 was installed together with kdegraphics, > and used to compile digikam against. No, I first uninstalled all that stuff like Arnd suggested. Then I run the svn-compile-script. Later I installed the other pieces one after the other to see what triggers the crash ... > > [...] > > Hope you will succeed and get digikam working, So do I :-) > because there is no > photograpic life without it under linux... ;-) I'm sure there are some people here loving to read this. So I just subscribe to it :-) Have a good time and enjoy it. Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Marcel Wiesweg
Hi Marcel,
On Monday 25 February 2008 20.02:06, Marcel Wiesweg wrote: > > So, something more I found out...: > > > > kdegraphics3 depends on libexiv2. If I just install libexiv2 (without > > kdegraphics3) svn digikam runs. If I install kdegraphics3 digikam > > crashes. > > > > Now I de-install libexiv2 but leaving kde3graphics installed (ignoring > > dependencies), digikam runs... > > > > So, it is a game between kdegraphics3 and libexiv2 that makes digikam > > crash. Each of the libraries alone is ok, but together not... > > > > Next I installed exiv2-0.16 from tar into /usr. That doesn't disturb > > digikam. But now konqueror, gwenview etc. are missing libexiv2.so.0, > > because I now have libexiv2.so.2. > > > > So I guess I'll have to uninstall exiv2-0.16 and reinstall suse's > > libexiv2 0.15-8.2 again, which will crash digikam but leave me a running > > system... > > That's exactly the kind of version mixup of libexiv2. Some KDE libs load > libexiv2.so.0, and digikam is compiled against libexiv2.so.2. It crashes > when loading so.0. For some reason the libs are binary incompatible, but > the linker does not notice. Why this is the case I leave to others to > comment (that means, I dont know). > I hope somebody will find a solution. However, now I am heading for another job in Barcelona tomorrow morning and will be back on my computer next weekend to try new suggestions - if any arrive meanwhile. thanks to you all for your help and work. Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com/en/linux.html Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: svn: crash when opening editor
|
|
In reply to this post by Marcel Wiesweg
Hello,
Anybody found any ideas how I can have the svn version and have the full kde running normally? kind regards Daniel On Monday 25 February 2008 20.02:06, Marcel Wiesweg wrote: > > So, something more I found out...: > > > > kdegraphics3 depends on libexiv2. If I just install libexiv2 (without > > kdegraphics3) svn digikam runs. If I install kdegraphics3 digikam > > crashes. > > > > Now I de-install libexiv2 but leaving kde3graphics installed (ignoring > > dependencies), digikam runs... > > > > So, it is a game between kdegraphics3 and libexiv2 that makes digikam > > crash. Each of the libraries alone is ok, but together not... > > > > Next I installed exiv2-0.16 from tar into /usr. That doesn't disturb > > digikam. But now konqueror, gwenview etc. are missing libexiv2.so.0, > > because I now have libexiv2.so.2. > > > > So I guess I'll have to uninstall exiv2-0.16 and reinstall suse's > > libexiv2 0.15-8.2 again, which will crash digikam but leave me a running > > system... > > That's exactly the kind of version mixup of libexiv2. Some KDE libs load > libexiv2.so.0, and digikam is compiled against libexiv2.so.2. It crashes > when loading so.0. For some reason the libs are binary incompatible, but > the linker does not notice. Why this is the case I leave to others to > comment (that means, I dont know). > > > Anyway I wonder why the svn installed in home looks > > after /usr/lib/libexiv2.so.0 (as in the backtrace of the crash)... > > > > kind regards > > > > Daniel Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |