GNOME Bugzilla – Bug 315968
Jpeg plugin crashes when "Save thumbnail" disabled
Last modified: 2008-01-15 14:04:28 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).
Created attachment 52074 [details] I used this file to reproduce the bug.
Works fine here with libexif 0.6.12, what version are you using?
I'm using the following Trustix RPMs: libexif-0.6.12-2ta libexif-devel-0.6.12-2ta
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.
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
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.
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.
Oh well, so much for that hypothesis.
Um, what is the "newest libexif from source" - CVS or 0.6.12?
I used 0.6.12, not CVS.
We're now at libexif 0.6.13 and GIMP 2.3.6. Has anything changed?
Let's assume that it is another incarnation of libexif brokenness. *** This bug has been marked as a duplicate of 300186 ***