Bug 250271

Summary: cannot print color document grayscale
Product: [I don't know] kde Reporter: S CITRIN <scitrin>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: scitrin
Priority: NOR    
Version: 4.5   
Target Milestone: ---   
Platform: unspecified   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description S CITRIN 2010-09-05 14:45:22 UTC
Version:           4.5 (using KDE 4.5.0) 
OS:                unspecified

In any kde application which uses a kde print dialog box, setting the page property to grayscale has no effect...the application will still try to print the document in color.

For example (steps to reproduce)
1.Open a color pdf document with Okular
2. File->Print->Options->Options and toggle Color Mode to  grayscale
3 Now print.
Document will still print in color, (thus increasing cost and possible wasting color ink).   I have confirmed this behavior on two different brands of printers with totally different cups ppd etc...(canon i560 and brother mfc-290c)

Also note, if you attempt to modify the  printer in systemsettings, to print grayscale by default, the option will not be persistent and will generally be ignored.  Returning to systemsettings after applying and saving the option, it will still be set to color and when bringing up the print dialog within a specific application, it will still be color by default. 

Archlinux (version: date bug filed...fully updated), kde 4.5.1 (not kdemod).   





Reproducible: Always

Steps to Reproduce:
See details..

Actual Results:  
1. Document still prints color when specified grayscale. 
2, Can't set printer default page properties to grayscale.

Expected Results:  
1. When printing, prints the document in grayscale.  

2. Grayscale printer property persistent if modified in systemsettings
Comment 1 S CITRIN 2010-09-05 20:31:33 UTC
Sorry, finally found it....duplicate 189014 (except for the systemsettings part which is probably another bug.)

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