Bug 145497

Created attachment 20586 [details]
Traceback

Could you try to install 0.9.2.beta3 to see if the problem persist?

can you send me a SPEC file for the RPM compilation? All SuSE packages are far behind, so I would build from tar

Hmm, I have no experience with SPEC files (this would be provided/created by the distributors). So maybe you could directly build from the tar file
(or svn)? 
See http://www.digikam.org/?q=download/svn
"Install digiKam in your Home Directory"

Had some problems compiling it, but in between 0.9.2 is out - same problem

Arnd, 

Look the backtrace of crash. It's relevant of Exiv2 shared lib, not digiKam directly:

Axel, update your computer with 

- Exiv2 0.13 release at least (0.14 will be better).
- Last libkexiv2 to last stable release 0.1.5.

Gilles

southpole:/home/axel # apt policy libkexiv2
libkexiv2:
  Installiert: 0.1.5-2.1
  Kandidat: 0.1.5-2.1
southpole:/home/axel # apt policy libexiv2
libexiv2:
  Installiert: 0.14-2.1
  Kandidat: 0.14-2.1

Created attachment 20936 [details]
Crash report after update

his is the latest traceback after the update (and restart)

Ok, now, a second try. Check if you haven't both release of Exiv2 installed on your computer...

Note : here i'm use Exiv2 0.14 and libkexiv2 0.1.5 without problem...

Gilles

southpole:/home/axel # rpm -qa *exiv2*
libexiv2-0.14-2.1
libexiv2-devel-0.14-2.1
libkexiv2-devel-0.1.5-2.1
libkexiv2-0.1.5-2.1

As you cahnged it to Metadata: First folder is an 'older' one, with still an preview icon in the tree view of digikam. Can that be a reason?

I changed a folder from anything to 0-anything, after the warning that anyting is not in the database anymore, digikam crashes immediately

Thanks for the backtrace - this indicates that the problem occurs
on the libexiv2 (just talked with Gilles on the IRC on this).

Therefore it seems that one of your images in the first folder
causes libexiv2 to crash.
To narrow the problem down, could you run
exiv2 image_name.jpg for each of the image files
to find out the problematic one?

Thanks a lot, Arnd

Exiv2 exception in print action for file picture.bmp:
picture.bmp: The file contains data of an unknown image type

Is that the problem?

might be ...
could you put that file somewhere to download?
(Gilles is surely happy to add this to his collection ;-),
and I could try this out here as well ...)

Best, Arnd

Well, seems that the last activity (renaming anything to 0-anything) did some sreious harm: I reverted everything, placed the content of the first folder into the backyard (so first folder is empty), removed ~/.kde/share/config/digikam*, removed (path)/digikam3.db, but on start it immediately crashes (after asking for the path to the pictures and creating the .db file). I'll attach another log.

Created attachment 20937 [details]
backtrace: First folder empty

Do you have other folders which have image files?
The last backtrace also points to exiv2...

Just to be sure, could you start again with a non-existing directory
for the images. Digikam should come up fine (and no call to exiv2
should be made, I would guess ...).

Axel,

Andreas, the Exiv2 lead developper, has recently fixed a similar bug in current implementation of libary. This is have been already reported in this room...

I recommend you to try the Exiv2 implementation from svn. 

1/ Uninstall old Exiv2 0.14
2/ Checkout source code, recompile and install Exiv2 from svn (look http://www.exiv2.org)
3/ recompile and install libkexiv2, kipi-plugins, and digiKam

I CC Andreas for informations.

Gilles Caulier

KExiv2Iface::KExiv2::load() calls 
Exiv2::ImageFactory::open() which apparently throws,
latest when it encounters the BMP file mentioned in note #12 (or was it note ~12)

Could it be that the Exiv2 exception is not caught?

-ahu.

Have the gurus sorted out who's chicken and who egg?
Meanwhile I went back to SuSE 10.0 delivery package: 0.7.anything. works again

Axel,

Can you give us fresh information about this report, to use last stable :
- Exiv2 0.15
- libkexiv2 0.1.5
- digiKam 0.9.2

Thanks in advance

Gilles Caulier

Hello Charles,
sorry for the delay, I first had to find a way to build exiv2 for SuSE 10.0.
Result is still the same: immediate crash
As coming from 0.7.x, I first deleted the old database and started digikam again. the log is attached.
Cheers
Axel

Created attachment 21532 [details]
backtrace with exiv2 0.15

One more: Starting from command line.

axel@southpole:~> digikam
terminate called after throwing an instance of 'Exiv2::Error'
  what():  /daten/2privat/Bilder/70 Jahre Nordparksiedlung/Thumbs.db: Die Datei enthält Daten eines unbekannten Bildtyps.
KCrash: Application 'digikam' crashing...

means nomething like: The file contains data of an unknown picture type

Axel,

Exiv2 generate an exception and it's not handle properlly by the libkexiv2 interface used by digiKam... Result digiKam crash.

This problem have been already reported in this roorm and fixed in current implementation from svn.

Look here : http://bugs.kde.org/show_bug.cgi?id=149267

and especially #2 with this patch :

http://websvn.kde.org/branches/extragear/kde3/libs/libkexiv2/libkexiv2/kexiv2.cpp?r1=704515&r2=704514&pathrev=704515

Gilles

Thanks for the info. Then you should close this bug with reference to bug 149267

Axel,

I will be happy if you can confirm than your problem is solved to apply patch: 

http://websvn.kde.org/branches/extragear/kde3/libs/libkexiv2/libkexiv2/kexiv2.cpp?r1=704515&r2=704514&pathrev=704515

It's must be apply on kexiv2.cpp from libkexiv2. It's easy to do. The binary compatibility is respected and you just need to recompile and install libkexiv2 (normally)

Gilles

*** This bug has been marked as a duplicate of 149267 ***

The latest version of libkexiv2 (0.1.5-26.2) fixes the problem. 
Thanks guys

Fixed with #149267