GNOME Bugzilla – Bug 691070
Attached JPEG file leads to crash when opened in German GIMP
Last modified: 2013-01-03 19:52:48 UTC
Created attachment 232638 [details] Output of "gimp --version --verbose" Dear colleagues, When I open the attached JPEG file screen_IMG_4718.JPG via File-->Open, GIMP crashes if I have set the UI language to German (de) via Edit-->Preferences-->Interface. Please find the error messages of the crash attached. If I change the UI language to en_US via Edit-->Preferences-->Interface and restart GIMP, I can open the JPEG file without errors. I have the problem only with this specific JPEG file. Other JPEG files work well. Regards, Frank
Created attachment 232639 [details] Screen-shot of the error messages during crash
Created attachment 232640 [details] JPEG file that leads to the crash when opening it (part 1)
Created attachment 232641 [details] JPEG file that leads to the crash when opening it (part 2)
Sorry guys, I had to split up the JPEG file (done via 7-Zip) due to file size.
Confirming. Locale-dependent handling of Exif data, maybe.
Freely translated into English, the error messages say something like this: - the plugin "file-jpeg.exe" has crashed - procedure "file-jpeg-load" has terminated without return values
Apparently Exif-related - if I remove the APP1 profile from the image (almost 1000kB - what is stored there for that image?), the image loads fine.
As it seems, it's a duplicate of bug #682454. In one of its other duplicates (bug #685485) the problem also disappeared after switching to the English UI. It is fixed in a newer build of GIMP 2.8.2, that you find at http://nightly.darkrefraction.com/gimp/. Please use the stable build (2.8) series and read the notes there. If this solves your problem, please mark this bug as duplicate of bug #682454.
I have exchanged file-jpeg.exe of my installation with the newer version from the nightly build gimp-stable-i686-2013-01-03.exe. Now, opening the JPEG file works also in German. I consider this bug being solved. Thanks to all! *** This bug has been marked as a duplicate of bug 682454 ***