Bug 989925

Summary: Normal grayscale printout mode fails with deskjet 895
Product: [Fedora] Fedora Reporter: Didier Lecardez <d.lecardez>
Component: hplipAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 15:07:27 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:
Attachments:
Description Flags
error_log none

Description Didier Lecardez 2013-07-30 07:37:10 UTC
Created attachment 780384 [details]
error_log

Description of problem:

Printing on a deskjet 895 fails in "normal grayscale".
Using "draft grayscale" , "draft color" , "normal color" is OK.

This worked in F14. To my knowledge, the problem started in FC15 and is still present.

This is very similar with https://bugzilla.redhat.com/show_bug.cgi?id=744338
that has been closed.

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

cups-pk-helper-0.2.4-2.fc19.i686
cups-filesystem-1.6.3-4.fc19.noarch
cups-filters-libs-1.0.35-3.fc19.i686
cups-filters-1.0.35-3.fc19.i686
cups-libs-1.6.3-4.fc19.i686
cups-1.6.3-4.fc19.i686
ghostscript-cups-9.07-10.fc19.i686

hplip-common-3.13.7-1.fc19.i686
hplip-3.13.7-1.fc19.i686
hplip-libs-3.13.7-1.fc19.i686
hplip-gui-3.13.7-1.fc19.i686


Steps to Reproduce:
1-Print a document using "normal grayscale" mode.
2-No printout is performed.
3-Errors appear in /var/log/cup/error_log

Actual results:


Expected results:
Have "normal grayscale" works with a Deskjet 895

Additional info:
See attached logfile

Comment 1 Tim Waugh 2013-08-01 15:07:27 UTC
bug #744338 is closed because it is now being tracked upstream. It hasn't yet been fixed.

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