Created attachment 59111 [details] Backtrace made with gdb Version: 1.9.0 OS: Linux I have my Collections on removable Media. After trying to scan for new Images digikam scans for about 30% then it crashes. That is almost the same folder that contains new images. These images open correctly in all other image viewers i have on the system ( gthumb / nautilus / shotwell ) Now im not able to work with new images because if digikam scans these folders containing new folders its crashing. That happens every time Ill try that. Reproducible: Always Steps to Reproduce: Start digikam - go to "Tools" the "scan for new images" Actual Results: It starts to scan...then at about 30% it crashes. Expected Results: New Image Folders should be found and presented in the Album View. It worked before and I have no clue what i have done to cause this. By the way exiv2 Version = 0.21.1
By the way: Im running on Ubuntu 10.10 with Gnome as Desktop.
We need a GDB backtrace to hack... Gilles Caulier
Created attachment 59135 [details] New Backtrace The BT is made as described in "https://wiki.edubuntu.org/Backtrace" Hopefully you can get some infos from it. Dikicam now doesnt close when getting the Backtrace..it freezes while tryint to scan the first new folder that still is not in the Treeview ( for what im doing the scan ) So after freezing I collected the Trace in the Terminal
Yes. trace is better now, but not yet suitable as well to hack. The crash is in Exiv2 shared lib. Go to Help/Component Info to see which version is used in digiKam. Exiv2 provide a command line tool to parse image metadata. Please try to reproduce the crash with this tool using an image from your collection, and give us a link to this image for future investigation. I CC Andreas Huggel who is lead Exiv2 developer... Gilles Caulier
Hi Gilles, thanks for your help. I did as you requested and here is the info from "about": digiKam version 1.9.0 Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: No Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes LibCImg: 130 LibClapack: internal library *LibExiv2: 0.19* LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.5.1 (KDE 4.5.1) *LibKExiv2: 1.1.0* LibKdcraw: 1.1.0 LibLCMS: 118 LibLensFun: external shared library LibLqr: internal library LibPGF: 6.09.44 - internal library LibPNG: 1.2.44 LibQt: 4.7.0 LibRaw: 0.10.0-Beta1 LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble widget: 0.10.1 Parallelized demosaicing: Yes Database backend: QSQLITE LibGphoto2: 2.4.10.1 LibKipi: 1.1.0 ------------------------------------------------- Opening a Terminal and using "exiv2 -V" i got another Version: *exiv2 0.21.1* Copyright (C) 2004-2011 Andreas Huggel So i dont know which is the right one .. ? The commandline test ist still waiting...i will do this asap... and get back to you. Best regards, Michael Gilles Caulier wrote: > https://bugs.kde.org/show_bug.cgi?id=271252 > > > Gilles Caulier<caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |ahuggel@gmx.net > Component|Database |libkexiv2 > > > > > --- Comment #4 from Gilles Caulier<caulier gilles gmail com> 2011-04-20 08:59:33 --- > Yes. trace is better now, but not yet suitable as well to hack. > > The crash is in Exiv2 shared lib. > > Go to Help/Component Info to see which version is used in digiKam. > > Exiv2 provide a command line tool to parse image metadata. Please try to > reproduce the crash with this tool using an image from your collection, and > give us a link to this image for future investigation. > > I CC Andreas Huggel who is lead Exiv2 developer... > > Gilles Caulier > >
It's clear. digiKam have been computed with an older Exiv2 (through libkexiv2 KDE interface) Exiv2 command line tool is the last Exiv2 : 0.21. digiKAm must use 0.21 of course. 0.19 is old and a lots of bugs have been fixed with 0.21. Please update/check your system... Gilles Caulier
Thank you Gilles, but now im lost - i don know how to update the system to a newer version of libkexiv2 to 0.21. I reinstalled digikam...tried to get Libexv2 over synaptic or direct download but then it says "dependencies couldnt be resolved.." something like this. At the moment I have the same level as before.. still dont know how to update Libexiv2 from 0.19 to 0.21. On an old Laptop I have Digikam 1.2 over the Software Center of Ubuntu 10.04 with 0.19 Libexiv and there are no probs... No I cant use Digikam..because I couldnt read any new folders. But I dont know how this came and from what effect - suddenly scanning doesnt work any more... (In reply to comment #6) > It's clear. digiKam have been computed with an older Exiv2 (through libkexiv2 > KDE interface) > > Exiv2 command line tool is the last Exiv2 : 0.21. > > digiKAm must use 0.21 of course. 0.19 is old and a lots of bugs have been fixed > with 0.21. > > Please update/check your system... > > Gilles Caulier
Hi Gilles, after not getting farther with trying to install the latest Exiv2 tool because i have different on my system now i tried to use the wonderfull doc on "http://scribblesandsnaps.wordpress.com/2011/03/09/install-the-latest-beta-of-digikam-on-ubuntu-10-10/" to install Digikam 2.0 and now everything works fine. At least the Folder scanning now works ! And thats what I missed. So I think it makes no sense bringing efforts in this "bug" if its gone with the new beta. ( maybe the Beta installed a new exiv2 version ?) So everything is good :-) Thank you very much Gilles or all you work ! best regards, Michael