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 301964 - Unable to open jpeg file
Unable to open jpeg file
Status: RESOLVED DUPLICATE of bug 300186
Product: GIMP
Classification: Other
Component: General
unspecified
Other Linux
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-04-25 19:27 UTC by Sergej Kotliar
Modified: 2005-04-26 13:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
File that can't be opened (185.65 KB, image/jpeg)
2005-04-25 19:29 UTC, Sergej Kotliar 		Details

Description Sergej Kotliar 2005-04-25 19:27:06 UTC 
Distribution/Version: FC4test2

Try to open the attached file
Comment 1 Sergej Kotliar 2005-04-25 19:29:08 UTC 
Created attachment 45668 [details]
File that can't be opened

It's a nice picture of me =)
Comment 2 mir 2005-04-25 22:21:15 UTC 
Same thing here.  GIMP 2.2.6, Gentoo, AMD64.  Seems to happen only to files with
EXIF data.

mir
Comment 3 mir 2005-04-25 22:43:50 UTC 
Removing EXIF with jhead fixes the problem:

jhead -de file.jpeg

mir
Comment 4 Michael Schumacher 2005-04-25 22:51:19 UTC 

*** This bug has been marked as a duplicate of 300186 ***
Comment 5 Sergej Kotliar 2005-04-26 13:28:33 UTC 
No, I don't think this is a duplicate, since this bug is a linux bug and totally unrelated to the GIMP 
installer on Windows.
Or am I just missing something here? Possible the cause is the same with libexif that needs to be fixed? 
Just wanted you to read this one more time to confirm that this is the same bug, cause it's not entirely 
obvious to me.
Comment 6 Michael Schumacher 2005-04-26 13:35:34 UTC 
See bug #300186 comment #35 and bug 300186 comment #37 

It is pretty obvious when you actually read the comments of this bug :)
Comment 7 Michael Schumacher 2005-04-26 13:37:09 UTC 
Argh, and you could really have read the comments before removing the duplicate.

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