[Digikam-devel] [Bug 136932] Access to a specific jpg photo crashed digikam

krienke at uni-koblenz.de krienke at uni-koblenz.de
Mon Nov 6 09:11:57 GMT 2006

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From krienke uni-koblenz de  2006-11-06 10:11 -------
Am Montag, 6. November 2006 09:48 schrieb Andreas Huggel:

> ------- Additional Comments From ahuggel gmx net  2006-11-06 09:48 -------
> Finally one that looks comprehensible, at least the reading part.
> Yes, I can reproduce the problem with the exiv2 utility and the image
> provided, will look into this.
> Did you use any software other than digikam to edit the image?
> If not, how exactly did you edit it; can you re-create similarly corrupted
> images with digikam?

I used digikam to edit the jpg comment and digikamimageplugins to enhance 
contrast. Thats all I did. I have a lot of other photos I edited in the same 
way and there are no similar problems. I even have a copy of this photo with 
the comment already included on another host and this version does not cause 
a crash (the size in bytes of both is identical). And I am quite sure, that I 
did not change anything else for this photo since I copied it to the other 
host. But  since I had quite a lot of digikam crashes (possibly the 
hyperthreading bug) when I worked on the photos of my holidays (of which 
dsc_3393.jpg is one) I guess that one of this crashes must have corrupted the 
photo in question.  Unfortunately I am unable to reproduce this problem, but 
anyway digikam should not crash when trying to extract the metadata of such a 
jpg even if the data contained in it are corrupt.


More information about the Digikam-devel mailing list