Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry.

[Tomas Pospisek]

Binary package hint: exiv2

When I start digikam from the command line, it bombs it with (thousands?) of messages like:

[...]
Warning: Directory NikonPreview, entry 0xb3b2 has unknown Exif (TIFF) type 46516; setting type size 1.
Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry.
[...]
Error: Offset of directory NikonPreview, entry 0x00c4 is out of bounds: Offset = 0x01010101; truncating the entry
Warning: Directory NikonPreview, entry 0x0504 has unknown Exif (TIFF) type 1798; setting type size 1.
[...]

According to http://mail.kde.org/pipermail/digikam-users/2009-July/007947.html

It's a problem of libexiv2
*t

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libexiv2-6 0.19-1
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
Uname: Linux 2.6.31-21-generic x86_64
Architecture: amd64
Date: Sun Jul 4 11:08:10 2010
ProcEnviron:
 LANGUAGE=de_CH:de
 PATH=(custom, user)
 LANG=de_CH.utf8
 SHELL=/bin/bash
SourcePackage: exiv2

[ariel (garcia)]

Reported upstream: http://dev.exiv2.org/issues/731

[ariel (garcia)]

Hi,

please see the upstream report here: http://dev.exiv2.org/issues/731

Short answer: exiv2 v0.20 is fine, it's a bug in Gimp which corrupts the picture's IFD field.

[Tomas Pospisek (tpo-deb)]

Hello Alan,

first, thanks for caring about this bug. Second, I'd be very happy if you
could tell me where this was fixed. Was it fixed upstream in some specific
version/git? In which version or which commit?

I'm asking, because I'm running Debian these days and so if I could
pinpoint the fix to some commit or version then I could also check it as
done for Debian.

Thanks again and best greetings,
*t

On Sun, 8 Mar 2015, Alan Pater wrote:

> ** Changed in: exiv2 (Ubuntu)
> Status: New => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/601555
>
> Title:
> Error: Directory NikonPreview, entry 0xb3b2 has invalid size
> 3115890614*1; skipping entry.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gimp/+bug/601555/+subscriptions
>

[Alan Pater (alan-pater)]

Apologies that I haven't explored exactly when it was fixed.

I tested with the images from https://bugzilla.gnome.org/show_bug.cgi?id=551636

Gimp (2.9.1) no longer corrupts the file.
Digikam (4.8) no longer bombs.

My libexif12 is version 0.6.21, released on 2012-07-12.

[ariel (garcia)]

@tpo-deb: the proble is still there in current Gimp 2.8.14-1+b1 from Debian testing/unstable. I guess we have to wait until the Jessy freeze is over for a fix.

$ exiv2 -pc a.jpg # original Nikon file

$ gimp a.jpg # cropped, saved as aa.jpg

$ exiv2 -pc aa.jpg
Error: Directory NikonPreview with 8224 entries considered invalid; not read.
Error: XMP Toolkit error 203: Duplicate property or field node
Warning: Failed to decode XMP metadata.

[Tomas Pospisek (tpo-deb)]

@ariel: but is the error message you are seeing the same problem?

The error message you are quoting is different then the one in the original bug report here. And the problem the error message is trying to tell us about does not seem to be the same:

   entry 0xb3b2 has unknown Exif (TIFF) type and invalid size

versus

    8224 entries considered invalid and Duplicate property or field node

?
*t

[ariel (garcia)]

@tpo-deb: you are right, I didn't notice that the messages differ somewhat. However, my point remains, Gimp 2.8.14 in Debian still corrupts the file "somehow"! The original Nikon file does not produce any warnings when read by exiv2, the gimp file does.

[Tomas Pospisek (tpo-deb)]

@ariel: I *think* it'd more effective to report the problem upstream @ http://www.gimp.org/bugs/ together with a photo image that can demonstrate the problem.