GNOME Bugzilla – Bug 764495
JPEG export: EXIF error
Last modified: 2016-11-26 19:26:50 UTC
After exporting image to JPG format some programs can't load them with error: Corrupt JPEG data: extraneous bytes before marker 0xed <file name> gimp -v --verbose GNU Image Manipulation Program версии 2.9.3 git-describe: GIMP_2_9_2-709-gcb76253 используя GEGL версии 0.3.7 (собранной с версией 0.3.7) используя GLib версии 2.48.0 (собранной с версией 2.48.0) используя GdkPixbuf версии 2.34.0 (собранной с версией 2.34.0) используя GTK+ версии 2.24.30 (собранной с версией 2.24.30) используя Pango версии 1.40.0 (собранной с версией 1.40.0) используя Fontconfig версии 2.11.94 (собранной с версией 2.11.94) используя Cairo версии 1.15.2 (собранной с версией 1.15.2)
Does this happen only with images you also imported from another JPEG, or with all images (also ones created from scratch)?
Searching the web there are some similar errors with the same message, but it's open whether the buggy files are from GIMP. Can you post the file before JPEG export and the exported JPEG file? What were the exact JPEG export options? Which programs complain about the JPEG file? Do they also complain when you export from GIMP 2.8.16?
(In reply to Michael Natterer from comment #1) > Does this happen only with images you also imported from another JPEG, > or with all images (also ones created from scratch)? This happens if original file imported from RAWtherapee. See attached files after few minutes.
Created attachment 325245 [details] Original file Image from HTC smartphone.
Created attachment 325246 [details] Exported by GIMP from original file No error
Created attachment 325247 [details] Exported by GIMP Error. Original file was open in RAWtherapee than exported to GIMP (without any transformation) and exported to JPG by GIMP (without any transformation)
Hello, I had the same error when opening in GIMP master the image from comment 6 (but it can still load it). Also opening the image metadata, the `metadata` window becomes all glitchy and slow, taking 100% of a CPU. The 2 other images are fine. And ImageMagick also outputs this same error (with comment `identify`). Nikolai > could you send us the image as exported from RAWtherapee? This way, we could see if the error is already present at this stage or if GIMP created a broken file. In any case, whether or not GIMP is responsible for the broken file, the metadata info window at least should not become crazy on a broken image.
Nikolai, we are waiting for this file.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!