Am Mittwoch, 4. Januar 2017, 17:21:38 CET schrieb Terry Jones: > After upgrade to 2.2.0 I experienced problems opening a film roll I had > previously edited with 2.0.3 and 2.0.6. > > Darktable would appear to start normally but would crash shortly of > opening the film roll.
Do you have a backtrace of the crash? > I eventually traced the cause to a single xmp file in the roll. When I > deleted that image and xmp file the problem disappeared. Just to check I > tried the same files on another computer that was still running > Darktable 2.0.3. The problem did not occur. > > > Reproducibility: > > The problem can be immediately reproduced by importing an image with the > associated xmp file contained in the attached tgz archive. The contents Works fine for me. > of the image file do not seem to matter. Certainly I tried it with > several Canon EOS 50D files and all produced the same result, but it may > need to be a 50D file to avoid creating inconsistencies between the > image and xmp file. > > The zip file also contains the the darktable log and cli output obtained > when starting darktable again after the import. The cli output indicates > a "double free or corruption" event has occurred. > > I can supply a copy of the original CR2 file if required, but it is > 22Mbytes so it may not email successfully. > > > Work Around: > > The work around for this problem is to: > > 1. Delete the image and xmp file. > 2. Restart Darktable and remove the image from the collection (Note: > There must be incorrect data in the database, as if the image file > is not also removed the problem still occurs). > 3. Replace the image file (but not the xmp file) > 4. Re-import and re-edit the image. > > > Cheers > > Terry Jones > > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to [email protected]
signature.asc
Description: This is a digitally signed message part.
