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.
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.