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 339299 - Update libexif in GIMP installer package
Update libexif in GIMP installer package
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Windows Installer
2.2.x
Other All
: Normal normal
: ---
Assigned To: Jernej Simončič
Jernej Simončič
: 345877 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-04-21 13:01 UTC by zillo77
Modified: 2008-01-15 13:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The file that generate the error (151.66 KB, image/jpeg)
2006-04-21 13:04 UTC, zillo77
Details

Description zillo77 2006-04-21 13:01:38 UTC
Please describe the problem:
I received a JPEG file from e-mail which GIMP 2.2.11 for Windows can't open.
I've uploaded this file here:
http://www.azpoint.net/Files_vari/glass_head_low.jpg
so you can get it for testing.
Every other software (Internet Explorer and Windows' Paint for example) can 
read this file and manage it correctly.
GIMP give me an error in "jpeg.exe" plug-in (the plugin crashes) and can't open 
the file. I think this Jpeg has a different "substandard" not supported by GIMP.
I'm using Windows XP SP2 and I'm using last GTK+ (v2.8.9 I think).

Steps to reproduce:
1. Install GIMP 2.2.11 with last GTK+ in Windows XP SP2 (or any Windows version 
I think)
2. Download Jpeg file from http://www.azpoint.net/Files_vari/glass_head_low.jpg
3. Try to open the Jpeg file with GIMP.


Actual results:
The jpeg.exe plug-in crashes and GIMP give the error that jpeg.exe crashed and 
can't open the file.

Expected results:


Does this happen every time?
Yes.

Other information:
Comment 1 zillo77 2006-04-21 13:04:50 UTC
Created attachment 64042 [details]
The file that generate the error

The file that generate the error
Comment 2 Simon Budig 2006-04-21 13:31:32 UTC
I can open it fine with gimp 2.2.10 on Linux. We have had a few of this kind of reports and usually the problem lies with libexif that is used to read the additional exif information in the JPEG file.

This particular file seems to have some corrupt exif tags:

simon@legends:~$ exiftags glass_head_low.jpg 
exiftags: Canon maker tag appears corrupt
exiftags: Canon maker tag appears corrupt
exiftags: Canon custom tag appears corrupt
Camera-Specific Properties:

Equipment Make: Canon
Camera Model: Canon EOS 10D
Firmware Version: 
Serial Number: 1930501097

Image-Specific Properties:

Image Created: 1980:01:01 00:04:18
Image Number: 501-0123

Please report, which version of libexif you are using and if an update fixes your problem.
Comment 3 Simon Budig 2006-04-21 13:43:43 UTC
Oh, please take a look at bug #300186 and check if this bug is a duplicate of that one.
Comment 4 zillo77 2006-04-21 16:08:40 UTC
Hi Simon,

First of all: 
in "C:\Programmi\GIMP-2.0\bin" folder I've this file:
libexif-10.dll (101KB)
It's the original file of GIMP 2.2.11 for Windows.

Second:
where can I find the update you are talking about?

Third:
I see you can open that image fine with GIMP 2.2.10 on Linux. But can you open that image with GIMP 2.2.11 on Windows (XP SP2)?

Finally:
in bug #300186 the problem wasn't fixed. I've tried to download the "libexif-12.dll" (251KB) linked in comment #40 (which solved the problem for that old bug), and renamed it in "libexif-10.dll" overwriting my original one, but it didn't fixed the problem.
So this bug isn't a duplicate of that one.
Comment 6 Simon Budig 2006-04-21 16:29:16 UTC
Frankly, I have no idea about GIMP on windows. I was referring to an libexif update, but I have no clue how this is done on windows. There are obviously some problems with the Exif data in the JPG file (exiftags wouldn't complain otherwise) so that makes libexif look guilty to me...

Some of the Windows Gimpers has to look at this. Schumaml?

Oh, the Windows screenshots unfortunately don't show a lot of good information. To really get an idea what happened you'd need to investigate this with a debugger.
Comment 7 Michael Schumacher 2006-04-21 17:51:39 UTC
The DLL for a current libexif would be named libexif-12.dll. So this is definetly an older version. The problem is that bug 300186 probably shouldn't have been closed, but kept as an ongoing "keep libexif up to date" bug for the Installer component thus making this report a duplicate.


I'll update the summary and reassign this bug accordingly.
Comment 8 Sven Neumann 2006-06-06 07:52:51 UTC
Has this been taken care of in the meantime? This report should at least be recognized by the maintainer of the Windows Installer and not be marked as UNCONFIRMED any longer.
Comment 9 Michael Schumacher 2006-06-06 08:09:59 UTC
Given that users still report libexif-10.dll as being installed, this has not been taken care of. 

Right now, the current version of libexif available from http://sourceforge.net/projects/libexif is 0.6.13.
Comment 10 Michael Schumacher 2006-06-25 14:19:51 UTC
*** Bug 345877 has been marked as a duplicate of this bug. ***
Comment 11 Sven Neumann 2006-07-20 07:48:16 UTC
Jernej, can you please comment on the state of this bug report?
Comment 12 Jernej Simončič 2006-10-18 08:08:40 UTC
Updated to 0.6.13 in GIMP 2.2.13 and 2.3.12.