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 616075 - plugin crash when trying to save indexed file as PNM
plugin crash when trying to save indexed file as PNM
Status: RESOLVED DUPLICATE of bug 606372
Product: GIMP
Classification: Other
Component: Plugins
2.6.7
Other Linux
: Normal critical
: 2.6
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2010-04-18 09:02 UTC by Eric
Modified: 2011-03-17 20:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
ScreenShoot GIMP (160.74 KB, image/png)
2010-04-19 00:43 UTC, Fabio Durán Verdugo 		Details

Description Eric 2010-04-18 09:02:10 UTC 
How to reproduce:
1. Create a new image.
2. Change the image's mode to indexed.
3. Try to save the image as PNM.

What happens:
1. GIMP displays a dialog box indicating that the file-pnm plugin has crashed.
2. A file is created containing the two bytes 'P6'.

What should happen:
1. GIMP should display a warning that the PNM file format does not support indexed color mode.
2. GIMP should offer to convert the indexed file to RGB and save it.
Comment 1 Fabio Durán Verdugo 2010-04-19 00:43:53 UTC 
Created attachment 159043 [details]
ScreenShoot GIMP

When I reproduce your steps I get this Image, This is your propost?
Comment 2 oliver 2010-04-24 20:09:50 UTC 
In current devel gimp (2.7.1), (but with some local changes to the code) no crash occurs.

Using Export, not Save, which is the new user-interface.

Functionality: 
ASCII-pnm is saved as pic, and can be viewed with pic-viewer.

BINARY-pnm is not correctly, containing some header bytes followed by 0xFF
until end of file.
Comment 3 Mukund Sivaraman 2010-10-07 13:00:50 UTC 
I can't reproduce any of this bug in the master branch.
Comment 4 Mukund Sivaraman 2011-03-17 20:20:16 UTC 
This seems to be a duplicate of bug #606372. Also see comment #3. I am unable to reproduce this bug in master, or the 2.6 branch.

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