Bug 315968 – Jpeg plugin crashes when "Save thumbnail" disabled

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 315968 - Jpeg plugin crashes when "Save thumbnail" disabled


Summary:	Jpeg plugin crashes when "Save thumbnail" disabled


Status:	RESOLVED DUPLICATE of bug 300186

Product:	GIMP
Classification:	Other
Component:	Plugins
Version:	2.3.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GIMP Bugs
QA Contact:	GIMP Bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-09-11 09:15 UTC by Rudolfs
Modified:	2008-01-15 14:04 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
I used this file to reproduce the bug. (18.02 KB, image/jpeg) 2005-09-11 09:17 UTC, Rudolfs	Details

Description Rudolfs 2005-09-11 09:15:02 UTC

Distribution/Version: Trustix 3.0

Steps to reproduce the problem:
1. Open a jpg file with EXIF data
2. "Save as", choose a different filename or location
3. Open "Advanced options" in the "Save as JPEG" dialog.
4. Uncheck "Save thumbnail"
5. Save

I get an error message:
GIMP Message
Plug-In crashed: "jpeg"
(/usr/local/opt/gimp-2.3.3/lib/gimp/2.0/plug-ins/jpeg)

The dying Plug-In may have messed up GIMP's internal state. You may want to save
your images and restart GIMP to be on the safe side.

GIMP Message
Saving '/dsc25411.jpg' failed:

Plug-In could not save image

The Gimp creates an empty jpg file (0 bytes long).

Comment 1 Rudolfs 2005-09-11 09:17:29 UTC

Created attachment 52074 [details]
I used this file to reproduce the bug.

Comment 2 Michael Natterer 2005-09-11 11:00:04 UTC

Works fine here with libexif 0.6.12, what version are you using?

Comment 3 Rudolfs 2005-09-11 11:12:37 UTC

I'm using the following Trustix RPMs:
libexif-0.6.12-2ta
libexif-devel-0.6.12-2ta

Comment 4 Michael Natterer 2005-09-11 12:30:21 UTC

Hm, ok, it isn't that easy :) Unfortunately we can't do much without
more information. Can you generate a stack trace of the crash?
Start gimp with (from devel-docs/debug-plug-ins.txt):

GIMP_PLUGIN_DEBUG=jpeg gimp-2.3

when the jpeg plug-in starts it will stop, printing its pid.
Then attach gdb using:

gdb /usr/local/opt/gimp-2.3.3/lib/gimp/2.0/plug-ins/jpeg <pid>

and enter 'c' (continue)

When the plug-in crashes, enter 'bt' and attach the output to
this bug.

Comment 5 Rudolfs 2005-09-11 15:58:02 UTC

I'm doing this the first time and I hope this is what you need:

Program received signal SIGSEGV, Segmentation fault.
exif_set_sshort (b=0x28 <Address 0x28 out of bounds>, 
    order=EXIF_BYTE_ORDER_MOTOROLA, value=272) at exif-utils.c:117
117                     b[0] = (unsigned char) value;
(gdb) bt

+ Trace 62933

#0 exif_set_sshort
at exif-utils.c line 117
#1 exif_set_short
at exif-utils.c line 126
#2 exif_data_save_data_content
at exif-data.c line 200
#3 exif_data_save_data
at exif-data.c line 839
#4 save_image
at jpeg-save.c line 443
#5 run
at jpeg.c line 466
#6 gimp_main
at gimp.c line 1790
#7 main
at jpeg.c line 62

Comment 6 weskaggs 2005-09-11 18:49:07 UTC

Hmm.  Because other people haven't yet replicated this problem, I am wondering
about what Trustix has done with their libexif rpm.  At the moment it seems
possible that this (and maybe your other jpeg-related bug report) is a
trustix-specific problem.

Comment 7 Rudolfs 2005-09-11 20:13:48 UTC

Strange, I removed the trustix libexif packages and compiled the newest libexif
from source, I also recompiled gimp 2.3.3 with --enable-debug --disable-print,
before I did the stack trace.

Comment 8 weskaggs 2005-09-11 20:18:59 UTC

Oh well, so much for that hypothesis.

Comment 9 Michael Schumacher 2005-09-14 20:29:00 UTC

Um, what is the "newest libexif from source" - CVS or 0.6.12?

Comment 10 Rudolfs 2005-09-15 06:01:54 UTC

I used 0.6.12, not CVS.

Comment 11 Michael Schumacher 2006-01-11 21:26:01 UTC

We're now at libexif 0.6.13 and GIMP 2.3.6. Has anything changed?

Comment 12 Michael Schumacher 2006-02-15 19:48:36 UTC

Let's assume that it is another incarnation of libexif brokenness.

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