GNOME Bugzilla – Bug 677066
error message trying to open jpeg file type with gimp 2.8
Last modified: 2012-11-29 15:31:24 UTC
Created attachment 215226 [details] error message trying to open jpeg file type error message trying to open jpeg file type, on windows xp sp3, recently installed, with gimp 2.8 installer for windows
Does this only happen with one JPEG file, or with any files?
If possible, please attach one of the jpeg files here.
Created attachment 216198 [details] Message when trying to open some jpeg-images.
I have got a similar problem. It onky happens with some jpeg files, not with any. Attached is the error message and a sample image. IMPORTANT: This problem does *not* appear if the interface language ist set to 'english [en_us]'! I've set it to 'english en_gb]' to produce an english error message. My system is running Windows XP SP3 German, and I am using GIMP 2.8.0.
Created attachment 216199 [details] Sample image causing the crash.
Probably a bug in libexif, related to the MakerNotes handling.
I can't get Gimp2.8 to even open anything but a .xcf file. Says jpg is unknown file type...And that's just one of several faults/bugs I've got now. Not happy.
On my Win7 x64 with Gimp 2.8.0 I was able to open the attached image #216199 (comment #5) by drag-dropping both with English as the interface language, as well as German. Thus, unable to reproduce.
kissaki0, where do you get your GIMP from?
The one linked to from the official websites download page http://www.gimp.org/downloads/ sf.net gimp-win project.
With language setting to 'english [en_us]' it works. I normally use German and get an error message that the plugin "file-jpeg.exe" crashed. Additional message: "Procedure 'file-jpeg-load' ended without return values"
Is this possibly a duplicate of bug #682454? If so, please mark this bug as RESOVLED DUPLICATE . Otherwise translate the reporters error message to English, please. Your answer during the next 6 weeks is appreciated. Thank you.
Yeah, seems like it's a duplicate. *** This bug has been marked as a duplicate of bug 682454 ***
*** Bug 689187 has been marked as a duplicate of this bug. ***