| Summary: | digiKam crashes after finding avi and so on | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Hartmut Krummrei <hartmut.krummrei> |
| Component: | Metadata-Video | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | axel.braun, caulier.gilles |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.0.0 | |
| Sentry Crash Report: | |||
|
Description
Hartmut Krummrei
2007-08-27 18:20:23 UTC
Hmm, I don't see these kind of problems... Which version of exiv2 (`exiv2 -V`) are you using? (Would you be able to compile current svn, there have been some improvements on crash handling in the connnection with exiv2?) Best, Arnd Hallo Arnd, exiv2 -V ergibt 0.14. Ich habe keine Ahnung, ob ich das Programm compilieren kann, ich habe es noch nie gemacht. War bisher nicht notwendig. Gibt es noch andere "Fehlerfinde-Hilfen", die ich Dir geben kann? Gruß Hartmut Arnd Baecker schrieb: [bugs.kde.org quoted mail] Hi Hartmut, better stick with English here, so that the real experts can help out ... Googling for "terminate called after throwing an instance of 'Exiv2::Error' " gives a couple of hits, it might be some inconsistent update of the components... What Kipi and KExiv2 and Exiv2 are listed under "Help"/"About" in digikam? Another shot in the dark: you could try to run kdeinit (just once) before starting digikam - sometimes it helps (though I am sceptical here ...) Does anyone else on OpenSuse see this problem? Hi Arnd, I will stick in english, did not know, that this is part of a discussion. "run kdeinit": no need for, becasuse digikam starts without problem, if there are now files ore only JPGs in its startfolder. For Exif2 GIFs and AVIs and anything else are unknown files, so there might be the reason for the crash. If digikam advises Exif2 to search for Exifdata in every file, the hole thing crashes. If there are only JPGs, Exif2 can respond with success and everything is OK. So to solve the problem digikam should first sort out all files and give Exif2 only those, which Exif2 knows. Perhaps one way araound ... Hartmut Arnd Baecker schrieb: [bugs.kde.org quoted mail] Well, for me everything works fine and I do have non-image files as well. To help you further, let me repeat my question above: "What Kipi and KExiv2 and Exiv2 are listed under "Help"/"About" in digikam?" Also, please try to run kdeinit just once. Sometimes it does help. While it is not the origin of the problem, in principle it would make sense to only use exiv2 on files it can handle, Gilles, what do you think? (Also note the related wish http://bugs.kde.org/show_bug.cgi?id=145743 ) Arnd, Hartmut We have found a problem with libkexiv2 if gcc -enable-visibility option is used during compilation. All Exiv2 C++ exception crash digiKam as well. Code is fixed in KDE3 branch. patch is here : http://websvn.kde.org/branches/extragear/kde3/libs/libkexiv2/libkexiv2/kexiv2.cpp?r1=704515&r2=704514&pathrev=704515 File to fix is kexiv2.cpp. patch is really simple. Binary compatibilty of libkexiv2 is preserved. Hartmut, it will be great if you can recompile libkexiv2 on your computer with this patch apply to confirm. Gilles Hi Gilles, I'll give it a try. The first try: configure output was checking for vsnprintf... yes checking for snprintf... yes checking for X... configure: error: Can't find X includes. Please check your installation and add the correct paths! Can anyone please tell me, what i have to install. I did a short check, but that did not help ... Hartmut Gilles Caulier schrieb: [bugs.kde.org quoted mail] Hartmut, You must recompile libkexiv2, not digiKam. libkexiv2 is a separate package used by digiKam. Look which version is installed on your computer, download the right tarball from sf, apply the patch, and compile/install it. https://sourceforge.net/project/showfiles.php?group_id=149779&package_id=221579 Gilles Hartmut,
>checking for X... configure: error: Can't find X includes. Please check
>your installation and add the correct paths!
Are you installed X11 developement package ?
Gilles
I'm working with libexiv2. The sources are in the right directory and I ran ./configure already. So the output you saw was from ./configure in the folder "/usr/src/packages/SOURCES/libkexiv2-0.1.5". So, I think I have to install a certain package, but I don't know the name of that package(s). I searched for x-development, but found nothing and in "development" there is to much ... Hartmut (I'm not used to compile, but am long enaugh in touch with Linux, so I know something about configure, make, make install ...) Hartmut Gilles Caulier schrieb: [bugs.kde.org quoted mail] Harmut, developement package use generally a suffix like "devel". If others OpenSuse users are in this room please confirm this point. Look in README file. There is a list of depencies to solve before to compile Gilles Gilles, two questions: 1. Have I to download the hole QT 3.3.x-source from Trolltech and compile it? 2. Or is it so, that I have to use the libkexiv-devel-packet? With Yast I did not find any libqt (I have several servers as sources) Hartmut Gilles Caulier schrieb: [bugs.kde.org quoted mail] Hartmut, >1. Have I to download the hole QT 3.3.x-source from >Trolltech and compile it? No. just install the Qt3-devel packages. No need to recompile all. smae way with KDE3-devel packages. >2. Or is it so, that I have to use the libkexiv-devel-packet? No. Gilles Gilles, I made it, digikam is running!!! Summary: What I had to know was what I had to install. 1. QT3-devel was easy to find. 2. KDE3-devel ist now kdelibs3-devel. And the configure-command told me to 3. install exiv2-devel. That was it. ./configure, make, make install, starting digikam and point it to my picture-folder with everything like .avi., .gif, .txt, .doc and so on.And digikam read everything and did not crash. Guys, that was hard work for me, but I'm glad, Icould do somthing to you and not only you for me ... Hartmut [bugs.kde.org quoted mail] Hartmut, Great to hear... And are you patched libkexiv2 ? gcc -enable-visibility option have been enable during compilation ? Gilles Gilles, I have patched the kexif2.cpp as advised, that was the idea ... Hartmut [bugs.kde.org quoted mail] Hartmut, And about gcc visibility option, it have been used during compilation ? give me a trace of compilation messages here ? thanks in advance Gilles Gilles, I don't know, wether or not the visibility-option has been used or not. As I said, I'm not used to compiling, so when I entered the make-command, I was just happy, that it ran without any errors. Fakt is, that digikam is running, thats what I wanted. If you want, I do the same thing tomorrow and send you the output. But you have to tell me, which files I have to delete to get make running once again. Hartmut Have a good night! [bugs.kde.org quoted mail] Hallo Gilles, I collected the output from make in an file. Do you want it and if, how? Hartmut [bugs.kde.org quoted mail] ok. it's fixed. i close this file now Gilles *** Bug 145497 has been marked as a duplicate of this bug. *** *** Bug has been marked as fixed ***. With 6.0.0, we have now a FFMpeg low level metadata parser based on libav C API for video files database registration. The Exiv2 video support is not used anymore as this code is buggous and nobody sound motivated in Exiv2 to finalize the code. The original post for this file must be fixed now and video metadata support with ffmpeg must be enough to populate database entries. Gilles Caulier |