Bug 308768 - Changing printer to "Print To File" should set printout to color
Summary: Changing printer to "Print To File" should set printout to color
Status: RESOLVED UPSTREAM
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: print-dialog (show other bugs)
Version: 4.9.2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-21 20:23 UTC by Kai Uwe Broulik
Modified: 2018-05-10 19:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2012-10-21 20:23:32 UTC
I have a black and white laser printer as default printer. Often I just print a PDF of something. When I open the printer dialog, the laserprinter is selected and since it is black and white, the printout is set to greyscale. When I change it to "Print To File (PDF)" it stays this way but when creating a PDF off something I think the user should explicitly have to set it to greyscale, otherwise it should be color.

Reproducible: Always

Steps to Reproduce:
1. Have a black and white printer and have it as default printer
2. Open some KDE app and click Print
3. Select "Print To File (PDF)" in the printer selection (also true for Postscript, I guess)
4. Don't touch the other settings
5. Print
Actual Results:  
The PDF is generated in greyscale

Expected Results:  
The PDF is generated in color. Only if I explicitly want it in greyscale (ie. open the advanced settings and say "Greyscale") it should be that way.
Comment 1 Michael Weghorn 2018-01-16 16:04:41 UTC
@Kai Uwe: Is this still a problem?
I think that this should be solved at the latest with the following change just integrated into Qt's "dev" branch: https://codereview.qt-project.org/#/c/215069
Comment 2 Michael Weghorn 2018-05-10 19:32:08 UTC
(In reply to Michael Weghorn from comment #1)
> @Kai Uwe: Is this still a problem?
> I think that this should be solved at the latest with the following change
> just integrated into Qt's "dev" branch:
> https://codereview.qt-project.org/#/c/215069

As mentioned, this should be fixed upstream now, so I'm closing this bug report. Please reopen in case you're still experiencing any issues with Qt versions >= 5.11.