[Digikam-users] svn: crash when opening editor
Daniel Bauer
linux at daniel-bauer.com
Sat Feb 23 17:07:13 GMT 2008
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 at venus:~> which digikam
> > /home/daniel/digikam/progs/bin/digikam
> >
> > daniel at 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/
More information about the Digikam-users
mailing list