GNOME Bugzilla – Bug 314463
jpeg.exe plugins crashed
Last modified: 2008-01-15 12:59:16 UTC
Please describe the problem: When ever I am trying to open a jpg file the jpeg.exe plugin crashes. Steps to reproduce: 1. Click on File --> Open 2. Go to a jpg folder and click on a file. 3. Click on Open Actual results: The program will say that the plug-in crashed Expected results: Open the file Does this happen every time? No Other information:
You aren't running the latest GTK+ release, are you? *** This bug has been marked as a duplicate of 300186 ***
GTK + version 2.6.8. This was according to where I downloaded it. How can I actually know for sure what version I am using?
I have just updated to GTK 2.8.0 and it is still happening
Is there a new version of jpeg.exe and where can I get it?
re-opening. Asking for new version of jpeg.exe
It probably isn't a function of which version of Gtk+ you are running, but rather a function of which version of libexif. Please try the suggestion in comment #40 of bug #300186.
Re comments #4 and #5, a new version of jpeg.exe is not going to help you if the problem is in a dll, which it almost certainly is. (The libexif dll, that is.)
The gtk+ installer available from http://gimp-win.sourceforge.net/stable.html should have the right version of libexif. If there's still a problem with that package, then this appears to be a new problem. You should then provide a JPEG that triggers the bug.
I have gotten the latest gtk. The stable version of gimp. libexif version from commect #6 above. I will attach the jpg that triggers my problem. thanks
can not attach my file. To big. can i send it directly to your email address?
You could at least have waited but you send it nevertheless. The file opens just fine here, so we have to assume that the error is not in the gimp plug-in but either in libjpeg or libexif. exifinfo shows one suspicious EXIF entry: User Comment |Invalid size of entry (8, expected 0 x 1). So it appears that the embedded EXIF info is not quite correct but of course libexif should handle this gracefully. And apparently it does so with the version I am using (libexif 0.6.12-2 from with debian sid).
I am sorry for not waiting for your reply. I am just so excited with using gimp and i can't use it until I fix the problem I am having. I am using windows and i can not find a windows version of the library. Do you have one and can you attach it? Thank you very much. Lawrence
I wouldn't touch Windows with a ten-feet pole.
Do you have problems with all jpeg files, or just files from one specific source (such as a specific digital camera)? If so, could you tell us what the source is?
Not happening to all jpeg files. Just with certail files.
And would you happen to have any insight as to what sort of files those might be?
According to comment 11 those that have bad exif. I have version 11 of libexif i can't seem to find a windows version of version 12. Do you have version 12 of the said library? Thank, Law
Ahem. Libexif is a rather flaky library, and there has been more than one problem identified with it. Not all of the problems are fixed in version 12. There is, for example, a problem that only affects images from Canon digital cameras or scanners, which is apparently not fixed in any version. So if the only files you have trouble with are images from your digital camera, it would be nice to know that, and to know the make and model of the camera. If you have trouble with files from multiple sources, it would be nice to know that as well.
I have a Canon Digital Rebel camera. I am not having problems with all my images. only some of them. I can not figure out what the commonality are. So only some from my camera.
In that case, this is probably a duplicate of bug #314018. Thanks for the information. Unfortunately, we may not be able to fix the problem until the libexif maintainers do something about it. *** This bug has been marked as a duplicate of 314018 ***