After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 684671 - JPEG won't load properly, cause file-jpeg-load to crash
JPEG won't load properly, cause file-jpeg-load to crash
Status: RESOLVED DUPLICATE of bug 682454
Product: GIMP
Classification: Other
Component: General
2.8.0
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-09-23 17:48 UTC by andrewmyles
Modified: 2012-11-08 20:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description andrewmyles 2012-09-23 17:48:03 UTC 
I'm currently working with lots of different images, most of them saved in JPEG format. Every once in a while, when trying to import these files into a image by drag-and-drop method, i got an error, gimp freezes for a while and I receive a message "file-jpeg-load did not returned value" (I'm using polish version, message might be different". If I open that image in an image viewer, like IrfanView and copy the image, then it is possible to paste it into gimp (2.8, BTW), as if it nothing has hapenned. I enclose an image that i'm trying to open.
Comment 1 andrewmyles 2012-09-23 17:52:52 UTC 
... or I don't. Appearently the image is too big. So, I'd had to scale it down to fit the 1000 kb limit.

BUT NOW THE IMAGE LOADS PERFECTLY IN GIMP.

So, choose, either you want samples to work on, or not.
Comment 2 Michael Schumacher 2012-09-23 18:11:35 UTC 
Did you remove the Exif data when scaling it down?
Comment 3 Max Mustermann 2012-11-08 20:57:23 UTC 
This bug is appearantly a duplicate of bug #682454.

It is fixed in a newer build of GIMP 2.8.2, that you find at http://nightly.darkrefraction.com/gimp/. If you'll have problems with big images again please use the stable build (2.8) series from there. 
I close your bug as duplicate of the bug #682454 now but please feel free to
report any further bugs you find.

*** This bug has been marked as a duplicate of bug 682454 ***