GNOME Bugzilla – Bug 309283
Gimp can't open some kind of JPEG pictures
Last modified: 2008-01-15 12:57:32 UTC
Please describe the problem: Whith the latest Cooker version of Gimp, I can't open some JPEG pictures with Gimp any more. Here is the message dialog I get : "Message GIMP L'ouverture de « /path/to/fleurs.jpg » a échoué : Le greffon n'a pas pu ouvrir l'image" Which means "Gimp message Failed to open « /path/to/fleurs.jpg » : the plugin could not open the picture" In the console I get the following message : $ gimp fleurs.jpg (gimp:18048): Gtk-WARNING **: Theme directory scalable/emblems of theme Flat-Blue has no size field /usr/lib/gimp/2.0/plug-ins/jpeg: fatal error: Segmentation fault You can test with the file at http://yhargla.free.fr/cpg133/albums/trucs/fleurs.jpg Here are some infos about it : size = 256590 bytes $ file fleurs.jpg fleurs.jpg: JPEG image data, EXIF standard 2.2 It looks like I can't open any EXIF 2.2 JPEG image any more. On the other hand I can still open JFIF 1.01 JPEG images. Ask any other details if needed. Steps to reproduce: 1. Download the file located at http://yhargla.free.fr/cpg133/albums/trucs/fleurs.jpg 2. Open it with gimp : $ gimp fleurs.jpg 3. See the plugin crash and the dialog appear Actual results: An error occurs, saying it can't open the file Expected results: I'd like to see my picture appear and be able to work on it Does this happen every time? Yes Other information: I already post it on Mandriva Bugzilla, see http://qa.mandrakesoft.com/show_bug.cgi?id=16618 According to Dick Gevers there are some buggy EXIF tags on the file. Removing EXIF tags solves the problem. But I think that the Gimp JPEG plugin should ignore these buggy tags rather than crash.
Works for me. Could it be that Cooker ships a known bad version of libexif? We had many problems with libexif 0.6.12 some time ago, so if they updated to this version, you might suffer from the same problems.
Unbelievable that there are still distributions shipping this buggy version of libexif. And almost as unbelievable that there are still users reporting this problem even though it has been reported hundreds of times already. *** This bug has been marked as a duplicate of 167699 ***