Comment 3 for bug 665006

Revision history for this message
Michael Hendry (hendry-michael) wrote : Re: [Bug 665006] Re: Corruption of files on export

On Fri, 2010-10-22 at 18:53 +0000, Jim Nelson wrote:
> To make it easier for other people, I'm reposting the links with URL
> encoding:
>
> http://rotarycupar.org/download/IMG004%20rescanned%20BAD.jpg
> http://rotarycupar.org/download/IMG004%20rescanned%20GOOD.jpg
> http://rotarycupar.org/download/IMG004%20rescanned%20ORIGINAL.jpg
>
> Also (since this might be a factor) can you tell me what parameters you
> used to export this file (size, quality, etc.)?
>
> Thanks,
>
> -- Jim
>
> ** Bug watch added: trac.yorba.org/ #2717
> http://trac.yorba.org/ticket/2717
>
> ** Also affects: shotwell via
> http://trac.yorba.org/ticket/2717
> Importance: Unknown
> Status: Unknown
>

Jim,

If I remember correctly, the first export of these files was with size
limited to 1200 and quality of 100%.

I've tried these parameters again, without reproducing the problem, so I
tried 90%, again with negative results.

I'm sure I didn't use 75% first time round, but this time the export of
all 46 files yielded one corrupt file - this time from a different
original.

I deleted all the exported files and tried again with settings of 1200
and 75%, and got this error message:

"Unable to export the following photo due to a file error.

/home/michael/DebugShotwell/IMG005 rescanned.jpg

Would you like to continue exporting?"

I said yes, and this time the previous file was exported correctly, and
although a file was apparently exported for "IMG005 rescanned.jpg", it
wasn't readable as a jpg.

Here are links to the set of files...

http://www.rotarycupar.org/download/IMG012%20rescanned%20BAD.jpg
http://www.rotarycupar.org/download/IMG012%20rescanned%20GOOD.jpg
http://www.rotarycupar.org/download/IMG012%20rescanned%20ORIGINAL.jpg

...this time with proper URLs!

Having cleared the export directory I tried again, and this time I got
warnings of file errors (as in the error message above) about two
completely different files, both of which had previously been
successfully exported.

At the next attempt, all files were successfully exported.

So the problem occurs frequently, but (so far) not reliably
reproducible.

Regards,

Michael