Red Hat Bugzilla – Bug 1018591
Fails to save image as PNG
Last modified: 2015-06-29 08:37:56 EDT
Description of problem:
Some images cannot be saved in PNG format.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start gimp, open /usr/share/backgrounds/gnome/Waves.jpg
2.Export as PNG
Error dialog, and this output:
lcms: skipping conversion because profiles seem to be equal:
libpng error: known incorrect sRGB profile
(file-png:3759): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
I have run into this issue too. It seems to be a problem with libpng and some .jpg files with particular color profiles.
Here are some additional references:
Created attachment 821292 [details]
jpg file with color profile that triggers bug
Attached image is a jpg file that has the color profile that triggers this bug.
Until this bug is fixed, a work around is to:
1) Load the problem source image
2) Select all, copy
3) Paste as new image
4) Discard original image and work with the pasted one that will not have the problematic color profile. If desired, export that on top of the original image.
Found a little simpler workaround for this problem:
1) Open the problematic JPG image
2) From the menubar choose Image -> Mode -> Convert to color profile...
3) In the dialog leave all options to default:
Convert to: RGB workspace (sRGB built-in)
Rendering intent: Perceptual
Black point compensation: unchecked
4) Hit convert
5) You should now be able to export to PNG without any problems
I've just seen this bug happen today. The first workaround solved it.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.