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 154576 - Certain jpeg files crash GIMP
Certain jpeg files crash GIMP
Status: RESOLVED DUPLICATE of bug 142252
Product: GIMP
Classification: Other
Component: Windows Installer
2.0.x
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-10-05 15:18 UTC by James Lavin
Modified: 2004-11-06 18:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Image that crashes GIMP 2.0.5 (Windows) (129.26 KB, image/jpeg)
2004-10-05 16:56 UTC, James Lavin
Details

Description James Lavin 2004-10-05 15:18:33 UTC
When I try to open a certain jpeg file, GIMP says "Opening xxx.jpg" but then
crashes with "jpeg.exe has encountered a problem and needs to close." I have
replicated this several times on my _WINDOWS XP_ machine.  Other jpegs work
fine.  (A perhaps related problem: I will re-install GIMP because my "Layers"
tool bar is no longer showing up when I start GIMP.)

I wasted hours searching for a virus (because "jpeg.exe" sounded a lot like a
virus to me!), but neither Spybot nor Avast! found anything suspicious. Someone
else (www.spinics.net/lists/gimpwin/msg03450.html) appears to have hit the same
bug.  If so, this bug seems related to a feature enhancement request that GIMP
support exif files. He writes:

I'm using W2000, v2.0.3

I'm unable to open some .jpg files,
specifically, camera images which have
been rotated.

(gimp-2.0.exe:828): LibGimpBase-WARNING **:
gimp-2.0.exe: wire_read(): error

the drwatson log appears to indicate
a problem in
function: exif_get_long
Comment 1 Michael Natterer 2004-10-05 15:39:38 UTC
If you closed your layers dialog, it would perhaps be a good idea
to just re-open it instead of reinstalling GIMP.
Comment 2 Michael Schumacher 2004-10-05 15:51:32 UTC
The problem with jpeg.exe seems to indicate that the libexif included in the
installer still isn't the latest version. Reassign this report the Installer
component?
Comment 3 Sven Neumann 2004-10-05 15:58:08 UTC
Since the reporter says that he's using v2.0.3, I guess that the version field
is set incorrectly. AFAIK newer versions of the Win32 installer ship with an
updated libexif that has this problem fixed.
Comment 4 James Lavin 2004-10-05 16:29:43 UTC
Thank you all for your excellent program and for your response to my report.

To clarify/elaborate:

1) I am using v2.0.5. Someone else posted the same problem using v2.0.3.

2) You seem to know how to fix this bug. If not, I hope you can improve the
error message. Seeing "jpeg.exe" made me fear the image I had just downloaded
had a JPEG virus. The problem itself is not major, but the error message is
frightening to people who don't know "jpeg.exe" is a sub-program within GIMP.

3) I never closed the layers dialog. It closed itself, apparently when this
glitch happened. But I was able to re-open it as comment #1 suggested. My bad. 
I had looked under File-->Preferences, not File-->Dialogs. (I'm obviously no
expert.)

Thanks again,

James
Comment 5 weskaggs 2004-10-05 16:39:41 UTC
The layers dialog thing is unrelated to the jpeg thing -- you almost certainly
closed it and didn't realize that you did.

Regarding the jpeg thing, could you please either attach the jpeg file here or
else give a link so that we can download it to test?  

We have, by the way, seen more than one problem caused by libexif, so there is
no guarantee that the report you quoted is caused by the same problem that you
are having.
Comment 6 James Lavin 2004-10-05 16:56:58 UTC
Created attachment 32252 [details]
Image that crashes GIMP 2.0.5 (Windows)

You can also find it online at: http://images.google.com/images?q=duct+tape

It's the picture with two rolls: "duct tape.jpg"
1080 x 720 pixels - 130k

(I saved it as duct_tape.jpg)
Comment 7 Sven Neumann 2004-10-05 17:24:15 UTC
Opens without any problems here on Linux so it is most likely a problem with
either libjpeg or libexif. Since the file contains EXIF info, this is most
likely another duplicate of bug #142252.
Comment 8 Sven Neumann 2004-11-06 18:56:34 UTC

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