Bug 1225858

Summary: [colord icc profile issue] gstoraster filter does not generate color output in RHEL7.1
Product: Red Hat Enterprise Linux 7 Reporter: Sanjay Kumar <sanjay.kumar14>
Component: ghostscriptAssignee: David Kaspar // Dee'Kej <deekej>
Status: CLOSED ERRATA QA Contact: QE Internationalization Bugs <qe-i18n-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: deekej, jpopelka, kkrothap, ovasik, psklenar, sanjay.kumar14, smaitra, twaugh
Target Milestone: rcKeywords: i18n
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ghostscript-9.07-19.el7 Doc Type: Bug Fix
Doc Text:
NO_DOCS
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 08:28:02 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1289025, 1305230, 1364088    
Attachments:
Description Flags
Cups error_log
none
Steps to reproduce and environment info
none
PPD File
none
Document used for printing
none
another cups error log
none
ghostscript-cups-icc-profile.patch none

Description Sanjay Kumar 2015-05-28 10:41:30 UTC
Created attachment 1031200 [details]
Cups error_log

Description of problem:
[colord icc profile issue] gstoraster filter does not generate color output in RHEL7.1

Version-Release number of selected component (if applicable):
1) ghostscript-cups-907-18
2) colord

How reproducible:


Steps to Reproduce:
1.Configure any HP inkjet printer 
2.Print and color document (using lpr command or from application)
3.See the printed output or output of gstoraster. 

Actual results:
Output is grayscale even though color option is selected while printing.

Expected results:
Printed output andoutput of gstoraster should be in color.

Additional info:
Please see the attached cups_error_log.
When we print any colored document (from application or using lpr), it gets printed in black ink only. While debugging this issue I found that, this issue is caused by “gstoraster” filter output.  Gstoraster outputs gray raster even though input to this filter is a colored PDF. While investigating it further I found that, this issue seems to be happening because of “-sOutputICCProfile=” switch getting added  in “gs” command. Please see the contents of cups_error_log from the attachment. 


-----------------------

D [27/May/2015:02:50:07 -0400] [Job 3] PPD uses qualifier 'RGB.Plain.'
D [27/May/2015:02:50:07 -0400] [Job 3] Calling FindDeviceById(cups-DeskJet_2130)
D [27/May/2015:02:50:07 -0400] [Job 3] Found device /org/freedesktop/ColorManager/devices/cups_DeskJet_2130
D [27/May/2015:02:50:07 -0400] [Job 3] Calling GetProfileForQualifiers(RGB.Plain....)
D [27/May/2015:02:50:07 -0400] [Job 3] Found profile /org/freedesktop/ColorManager/profiles/DeskJet_2130_RGB__
D [27/May/2015:02:50:07 -0400] [Job 3] Calling org.freedesktop.ColorManager.Profile.Get(Filename)
D [27/May/2015:02:50:07 -0400] [Job 3] Use profile filename: ''
D [27/May/2015:02:50:07 -0400] [Job 3] Using ICC Profile ''
D [27/May/2015:02:50:07 -0400] [Job 3] Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -sOutputType=0 -r600x600 -dMediaPosition=1 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=841 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=17 -dcupsInteger0=26 -scupsPageSizeName=A4 -I/usr/share/cups/fonts -sOutputICCProfile= -c -f -_
D [27/May/2015:02:50:07 -0400] [Job 3] envp[0]="CUPS_CACHEDIR=/var/cache/cups"

Comment 2 Tim Waugh 2015-06-09 06:54:55 UTC
Please provide a complete test-case that demonstrates the problem. In particular, could you please provide the PPD file you are using, from the /etc/cups/ppd/ directory, as well as a PDF input file you see printed incorrectly. Thanks!

Comment 3 Tim Waugh 2015-06-09 06:56:29 UTC
Changing component to cups-filters as it looks like the gstoraster filter may be at fault.

Comment 4 Sanjay Kumar 2015-06-10 09:11:11 UTC
Created attachment 1037179 [details]
Steps to reproduce and environment info

Comment 5 Sanjay Kumar 2015-06-10 09:11:59 UTC
Created attachment 1037180 [details]
PPD File

Comment 6 Sanjay Kumar 2015-06-10 09:13:01 UTC
Created attachment 1037181 [details]
Document used for printing

Comment 7 Sanjay Kumar 2015-06-10 09:14:10 UTC
Created attachment 1037182 [details]
another cups error log

Comment 8 Tim Waugh 2015-06-18 16:32:56 UTC
Changed component back to ghostscript. Actually 'gstoraster' comes from the ghostscript package in Red Hat Enterprise Linux 7.

Comment 9 Tim Waugh 2015-06-18 16:34:16 UTC
Created attachment 1040579 [details]
ghostscript-cups-icc-profile.patch

I think this should fix it.

Comment 10 Sanjay Kumar 2015-06-22 12:52:43 UTC
Hello Tim,

Thanks for the patch. Applying the attached patch to upstream package (9.07 version), seems to fix the issue but I dont see "Using icc Profile '' " message in the error_log file after replacing existing gstoraster with newly compiled gstoraster. Can you share ghostscript-cups package after applying patch for RHEL 7.1 x86_64 bit so that I can test it one more time .

Comment 12 Sanjay Kumar 2015-07-02 06:10:58 UTC
Even other users have also started facing this issue.

https://bugs.launchpad.net/hplip/+bug/1469677

Comment 16 David Kaspar // Dee'Kej 2016-07-20 13:43:48 UTC
Hello Sanjay,

could you please try to test this problem again with this scratch-build packages?
> https://dkaspar.fedorapeople.org/share/scratch-build/rhel/7.2/ghostscript/

I'm unable to verify the fix, because I do not have any HP InkJet available for testing at the moment.

NOTE: These packages are for *TESTING PURPOSES ONLY*, they're not to be used in production environment!!

Thank you very much in advance,

David

Comment 22 David Kaspar // Dee'Kej 2016-09-08 11:01:37 UTC
Hello Sanjay,

this is a reminder that we need you to test the provided scratch build packages. We do not have any hardware where we could test this issue & patch.

Unless we hear from you in some reasonable time, we will be forced to drop this BZ from advisory, and I can't guarantee it would make it back to next RHEL6 major update.

Thank you for your understanding.

Best regards,

David

Comment 24 Satyabrata Maitra 2016-09-09 07:28:13 UTC
Restoring the NEED_INFO to Sanjay Kumar, raised by David. While answering Krishnababu's query, all need_info requests nullified.

Comment 25 Satyabrata Maitra 2016-09-14 13:03:38 UTC
Hi David

RHEL7.3 is on snapshot-4 stage now. So, we would require blocker+ only, to accept any fix. In case this bug is a blocker for RHEL7.3 release, please request for blocker.

Regards
Satya

Comment 26 David Kaspar // Dee'Kej 2016-09-14 15:09:00 UTC
Hello Satya,

in this case, I would prefer to drop this BZ out of advisory. Since the reporter is not answering, I guess we can consider this as being not so important anymore.

Regards,

David

Comment 37 errata-xmlrpc 2016-11-04 08:28:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2550.html

Comment 38 Red Hat Bugzilla 2023-09-14 02:59:49 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days