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 677583 - Desaturated result show in GIMP doesn't match what is saved.
Desaturated result show in GIMP doesn't match what is saved.
Status: RESOLVED NOTABUG
Product: GIMP
Classification: Other
Component: General
2.8.0
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-06-06 20:47 UTC by Lyle Kroll
Modified: 2012-06-07 10:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
7z files which include the target and the screenshot that shows the problem. (527.05 KB, application/x-zip-compressed)
2012-06-06 20:47 UTC, Lyle Kroll 		Details

Description Lyle Kroll 2012-06-06 20:47:33 UTC 
Created attachment 215775 [details]
7z files which include the target and the screenshot that shows the problem.

I've noticed this before but after doing another monochromatic, I had to start this bugzilla.   Not the posterline in the sky; the saved jpeg result is much cleaner and doesn't show it.   Not sure why what's displayed does not match which is saved (and sort of glad the saved result is better, but...).   Hopefully you can verify this and recommend a work-a-round.   This example is an IR simulation that I'm trying to perfect.    Just open the saved jpeg result in GIMP and you will see the issue; used your internet browser or other viewer like Irfanview and all is good.    :)

ref:  http://www.fontplay.com/freephotos/thirteen/fp060108-21.jpg
Comment 1 Lyle Kroll 2012-06-07 09:30:58 UTC 
OK; Offnuts (GIMPChat) suggested that it could be my color management settings.   Indeed, I had color managed display enabled so I changed the setting to no color management and voila; issue no longer there.   Not sure why color management caused this display issue but it did so I guess it's not a but but a feature.    :)
Comment 2 Lyle Kroll 2012-06-07 09:31:35 UTC 
OK; Ofnuts (GIMPChat) suggested that it could be my color management settings.   Indeed, I had color managed display enabled so I changed the setting to no color management and voila; issue no longer there.   Not sure why color management caused this display issue but it did so I guess it's not a but but a feature.    :)
Comment 3 Lyle Kroll 2012-06-07 09:31:39 UTC 
OK; Ofnuts (GIMPChat) suggested that it could be my color management settings.   Indeed, I had color managed display enabled so I changed the setting to no color management and voila; issue no longer there.   Not sure why color management caused this display issue but it did so I guess it's not a but but a feature.    :)
Comment 4 Lyle Kroll 2012-06-07 09:39:25 UTC 
Just realized I can't do this; if I choose no color management, then aRGB images won't automatically get converted to sRGB (which is the behavior that I want).   So back to being a bug.
Comment 5 Lyle Kroll 2012-06-07 09:51:19 UTC 
OK; sorry for all the multiple entries earlier too.   I looked at my color management settings again and for some reason, I had chosen monitor for color management.  I changed both RGB profile and monitor profile to sRGB IEC611966-2.1 and all is well again.   This color management stuff seems more complicated an issue then it was in GIMP 2.6x.   Now it appears to be a feature again.   Still weird.  :)