shotwell Error: Directory NikonPreview with 8224 entries considered invalid; not read

[mabab]

Binary package hint: shotwell

When I start shotwell and want to import images, I get the following error:

Error: Directory NikonPreview with 8224 entries considered invalid; not read.
Error: Directory NikonPreview with 8224 entries considered invalid; not read.
Error: Directory NikonPreview with 8224 entries considered invalid; not read.
Error: Directory NikonPreview with 8224 entries considered invalid; not read.
Error: Directory NikonPreview with 8224 entries considered invalid; not read.
Segmentation fault

With gimp and eog I can open these images.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: shotwell 0.7.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx wl
Architecture: amd64
CheckboxSubmission: 7af25d8dc93be46c57e9d24c09badf1b
CheckboxSystem: a8eb386cdae417b3356c1f6b8c73686f
Date: Wed Oct 13 08:17:23 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: shotwell

[Jim Nelson (yorba-jim)]

This is actually two separate problems.

The error messages you're seeing are not fatal errors, but warnings coming from Exiv2, the metadata library Shotwell uses. Even if you see them, that does not automatically mean the photo will not be imported (in fact, we will import any photo even if no metadata is read). We cannot control the output of these messages (yet). This ticket is for that: http://trac.yorba.org/ticket/1872

The problem of a segfault is, obviously, much more serious. Can you reproduce this quickly? How many photos does it import before segfaulting?

If you could run Shotwell like this:

$ SHOTWELL_LOG=1 shotwell

reproduce the problem, and then attach this file to this ticket:

~/.cache/shotwell/shotwell.log

that would help me greatly. (The log might help me pinpoint which file is causing the problem.)

[mabab (mabab)]

I got the following message from shotwell:

18050 Duplikate der Fotos nicht importiert:

/home/matthias/Bilder/dscn0292.jpg
/home/matthias/Bilder/erstes_smiley.jpg
/home/matthias/Bilder/2003/Betriebsausflug Wöhlerschule Kollegium 10.10.03/p1010304.jpg
/home/matthias/Bilder/2003/Betriebsausflug Wöhlerschule Kollegium 10.10.03/p1010300.jpg
(und 18046 andere)

9 Fotos konnten wegen Datei- oder Hardwarefehler nicht importiert werden.
/home/matthias/Bilder/f-spot Bilder nicht löschen/2005/09/15/dscn1979.jpg
/home/matthias/Bilder/WIR/2005/2005_09/2005-09-17/dscn1983.jpg
/home/matthias/Bilder/WIR/2005/2005_09/2005-09-17/dscn1986.jpg
/home/matthias/Bilder/WIR/2005/2005_09/2005-09-17/dscn1987.jpg
(und 5 andere)

[mabab (mabab)]

Here is the output of the terminal.

[Jim Nelson (yorba-jim)]

Did it segfault this time? It looks like it didn't.

Were any photos imported? Because it's seeing so many duplicates I suspect your seeing this problem: http://trac.yorba.org/ticket/2587

-- Jim

[mabab (mabab)]

I deleted $HOME/.shotwell and made an import of my pictures again. The program finished but in the end I had to kill it. I attach the log, the terminaloutput and the output of the programm.

[mabab (mabab)]

terminaloutput

[mabab (mabab)]

Graficaloutput

[Jim Nelson (yorba-jim)]

Due to the number of images you're importing, I suspect the segfault is due to a memory leak we've fixed in trunk. The ticket for that is here: http://trac.yorba.org/ticket/2566 The duplicates I believe are due to the ticket I mentioned earlier (which hopefully will be fixed in time for 0.8).

[mabab (mabab)]

I tried shotwell 0.8. Same problem. But I can start and automatically scan my library till crash. Then start again and again. After a while and a lot of crashes it indexed all my pictures.

[Adam Dingle (adam-yorba)]

mabab,

we're about to release Shotwell 0.8.1, which I hope will fix this crash. You can get the code like this:

$ svn co svn://yorba.org/shotwell/branches/shotwell-0.8

If you're able to build from source, it would be great if you could build this version and see if the crash you're seeing is fixed.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Konôpka (martin.konopka)]

This is not a Shotwell bug. It is a bug in exiv2. I have just encountered it on the latest development version of ubuntu (to become 14.04 LTS), 64-bit version. Bug 662216 says nothing about exiv2 (which serves, I guess, as a backend for Shotwell). However, I use exiv2 directly. My way to see the bug:

1.) Open a terminal and go to a directory in which you store JPEG photos from a Nikon digital camera.
2.) Try to change the file's timestamp using the command
exiv2 mv -T myfile.jpg

The program makes its job correctly, but not without seriously looking complaints:

"Error: Directory NikonPreview with 8224 entries considered invalid; not read."

The message states that it is an ERROR, not a warning.

[Jim Nelson (yorba-jim)]

Martin, please re-read my comment in #2. Although labelled as an error by Exiv2, it is not an error in the sense that (a) Shotwell can still import and view these photos, and (b) Shotwell (via Exiv2) can still read the majority of the metadata in the photos. The "NikonPreview" directory is a section of the metadata that is Nikon-specific and not used by Shotwell.