Bug 1036321

Summary: iCCP: known incorrect sRGB profile
Product: [Fedora] Fedora Reporter: rvcsaba
Component: timelineAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gwync, neteler, swt
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:17:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Pop-up window with error message none

Description rvcsaba 2013-11-30 22:01:09 UTC
Created attachment 831057 [details]
Pop-up window with error message

Description of problem:

If I started timeline, I get a popup window:

Python Warning

iCCP: known incorrect sRGB profile


Version-Release number of selected component (if applicable):

timeline-1.0.1-1.fc20.noarch


How reproducible:

Always. Start timeline.


Actual results:

Get error message.


Expected results:

No error message.

Comment 1 Elia Devito 2013-12-26 00:09:31 UTC
I have encountered this problem with PlayOnLinux

Comment 2 Elia Devito 2013-12-26 00:27:30 UTC
http://www.libpng.org/pub/png/libpng-manual.txt


Error detection in some chunks has improved; in particular the iCCP chunk
reader now does pretty complete validation of the basic format.  Some bad
profiles that were previously accepted are now rejected, in particular the
very old broken Microsoft/HP sRGB profile.  The PNG spec requirement that
only grayscale profiles may appear in images with color type 0 or 4 and that
even if the image only contains gray pixels, only RGB profiles may appear
in images with color type 2, 3, or 6, is now enforced.  The sRGB chunk
is allowed to appear in images with any color type.

Comment 3 Elia Devito 2013-12-26 00:28:26 UTC
http://www.playonlinux.com/en/issue-2839.html

Comment 4 markusN 2014-02-04 08:16:13 UTC
Among others, also spyder-2.2.4-1.fc20.noarch and
VirtualBox-4.3.6-4.fc20.x86_64.rpm are showing this issue.

Potential solution in the second comment 

http://tex.stackexchange.com/questions/125612/warning-pdflatex-libpng-warning-iccp-known-incorrect-srgb-profile

Comment 6 rvcsaba 2014-08-16 21:52:50 UTC
(In reply to markusN from comment #4)
> Potential solution in the second comment 
> 
> http://tex.stackexchange.com/questions/125612/warning-pdflatex-libpng-
> warning-iccp-known-incorrect-srgb-profile

Thanks!

My problem solved this command line bash script:

rpm -ql timeline | grep '\.png$' | while read; do mogrify -strip "$REPLY"; done

Comment 7 markusN 2014-08-17 16:30:39 UTC
Thanks rvcsaba (comment #6):

Sweet - I cleaned also the "spyder" PNG profile warnings like using your method:
rpm -ql spyder | grep '\.png$' | while read; do mogrify -strip "$REPLY"; done


Furthermore tried the same on "VirtualBox":

rpm -ql VirtualBox | grep '\.png$' | while read; do mogrify -strip "$REPLY"; done

However, here one or so PNG files still issue(s) the warning. I tried:

repoquery --requires --recursive --resolve VirtualBox | sort | xargs rpm -qil | grep '\.png$' | xargs identify

but I didn't manage to get rid of it. Also no success with "lsof". Hints welcome for VirtualBox.

Comment 8 rvcsaba 2014-08-19 23:13:19 UTC
(In reply to markusN from comment #7)

I use this (root login), work it:

rpm -ql VirtualBox-4.3 | grep '\.png$' | xargs mogrify -strip

(I use VirtualBox-4.3 from virtualbox.org.)

Comment 9 rvcsaba 2014-08-21 17:00:23 UTC
Eh...:

... | xargs -n1 mogrify -strip

Sorry.

Comment 10 markusN 2014-08-21 23:44:43 UTC
So, trying your suggestion on the RPM from "RPM Fusion" (based in VirtualBox-4.3.14-1.fc20.src.rpm) as:

rpm -ql VirtualBox-4.3 | grep '\.png$' | xargs -n1 mogrify -strip

... I still get tons of
Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile

at startup of VirtualBox and when clicking on icons. It must come
from another package...

Comment 11 Scott Talbert 2015-02-02 04:50:35 UTC
It appears this has been addressed upstream for timeline, according to the changelog:
http://thetimelineproj.sourceforge.net/changelog.html

Comment 12 rvcsaba 2015-02-02 09:46:34 UTC
Please build latest 1.4.0 release!

Comment 13 markusN 2015-03-04 21:21:39 UTC
FWIW, for Virtualbox, there is an upstream ticket:

https://www.virtualbox.org/ticket/12610
"Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile"

Comment 14 Fedora End Of Life 2015-05-29 09:53:23 UTC
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'
of '20'.

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.

Comment 15 Fedora End Of Life 2015-06-29 13:17:56 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.