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 169930 - Jpeg plugin crashing
Jpeg plugin crashing
Status: RESOLVED DUPLICATE of bug 167699
Product: GIMP
Classification: Other
Component: Plugins
2.2.x
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-03-11 11:49 UTC by breehee7
Modified: 2008-01-15 12:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description breehee7 2005-03-11 11:49:21 UTC 
Distribution/Version: XP Pro Version 2002 Service pack 2

Attempting to open an image without exif information caushes the Jpeg plugin to
crash.
I had reported the same bug earlier. Received notice that it was fixed.
Apprently this was due to a faulty installer.
Sadly the problem still exist. If requested, I can supply a sample of an image
causing this problem, as well as a more detailed list of my hardware.
Comment 1 breehee7 2005-03-11 11:57:00 UTC 
Tried to attach an image (2.5MB) too large. Can be submitted separately, if
requested.
Comment 2 Michael Schumacher 2005-03-11 12:11:40 UTC 
All reports so far hve been about problems with images containing EXIF data.
What bug report are you refering to?
Comment 3 breehee7 2005-03-11 12:25:22 UTC 
Received the following e-mail after first reporting this. See below:
Jernej Simoncic changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|                            |FIXED
             Status|ASSIGNED                    |RESOLVED



------- Additional Comments From Jernej Simoncic  2005-03-03 17:40 -------
Fixed in 2.2.4

------- You are receiving this mail because: -------
You are on the CC list for the bug.
Comment 4 Michael Schumacher 2005-03-11 12:31:02 UTC 
The number of the other bug report would have been more useful than an excerpt
of a status mail for it :)
Comment 5 Manish Singh 2005-03-11 19:00:13 UTC 
The reporter means bug #164053, but the original bug reported is bug #167699.
I'm going to reopen that and resolve this as a duplicate.

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