Bug 368758 - Grayscale option ignored when generating print data for PDF document
Summary: Grayscale option ignored when generating print data for PDF document
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: printing (show other bugs)
Version: 0.25.80
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
: 390409 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-13 19:17 UTC by Francisco Gonzalez
Modified: 2023-03-04 03:45 UTC (History)
12 users (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 Francisco Gonzalez 2016-09-13 19:17:26 UTC
Trying to print a color pdf document in grayscale produces a color printing. This happens when printing to a color printer and also printing to a file. Printing a png file in grayscale works as expected. 

Reproducible: Always

Steps to Reproduce:
1. Open a pdf color file
2. Select "File -> Print -> Options -> Options -> (Color Mode) Grayscale"
3. Press "Print"

Actual Results:  
The document is printed in color

Expected Results:  
The document should be printed in grayscale

Tested in Archlinux with version 0.26.0
Frameworks 5.25.0
Plasma 5.7.5
PDF Backend 0.6.5
KDE Development Platform 4.14.24
kdelibs 4.14.24
Comment 1 Alexis M. 2017-01-23 21:00:04 UTC
Confirmed on Archlinux 

Also, duplex printing won't work from the okular print wizard.

Okular 16.12.1-1
Linux 4.8.13-1
Plasma 5.8.5.1
Frameworks 5.30.0-1
kdelibs 4.30.0-1

Printer: Brother MFC-J5620DW
Driver: 3.0.1-2
Comment 2 csbugs 2017-08-15 14:44:16 UTC
I can confirm this in Opensuse Leap 42.3 using
- kde-print-manager-17.04.2-1.1
- okular-17.04.2-1.6
- Plasma 5.8.7
- plasma-framework 5.32-0-4.1
- libQt5.6.2
- kdelibs-4.14.33

In evince it works though using gtk oder gnome(?) print dialog...

Is this related to https://bugreports.qt.io/browse/QTBUG-54464 ?
Comment 3 Nate Graham 2017-09-29 01:01:57 UTC
*** Bug 369115 has been marked as a duplicate of this bug. ***
Comment 4 Dainius Masiliūnas 2017-12-03 14:17:22 UTC
I can confirm both issues on openSUSE Leap 42.3. If either the greyscale option worked OR the advanced printing tab was there, it would be possible to print greyscale PDFs. As it is, CUPS defaults need to be changed instead, and that's way too involved for such a simple task...
Comment 5 Oliver Sander 2017-12-04 10:52:57 UTC
As a workaround, if you have a recent version of Okular [0], grayscale printing should work if you set the 'force rasterization' option.

[0] You need the patch 0c4c2ddbbc5e509c69b72c99bf6e83a356669eba , which dates from August 4th, 2017
Comment 6 Michael Weghorn 2018-01-17 13:30:06 UTC
Note that the "Advanced" options tab has been reintroduced for the current development version of Qt 5 [1]. Also, the problem with duplex [2] and color [3] options being set at different places has been fixed, so I'd expect that the problem should be solved with those Qt upstream changes (will be part of the upcoming Qt 5.11) for the case where a real printer is involved.

[1] https://codereview.qt-project.org/#/c/213391/
[2] https://codereview.qt-project.org/#/c/215131/
[3] https://codereview.qt-project.org/#/c/215069
Comment 7 Nate Graham 2018-01-17 14:04:27 UTC
Should we close this as RESOLVED UPSTREAM, then?
Comment 8 Michael Weghorn 2018-01-17 14:58:41 UTC
(In reply to Nate Graham from comment #7)
> Should we close this as RESOLVED UPSTREAM, then?

While printing to real devices should yield the expected result now, Okular itself still does not take the color/greyscale into account when generating the print data (by default, s. Oliver's comment 5 for rasterized printing), which also leads to "Print to file (PDF)" still not yielding the expected result. (Sorry for not mentioning that more explicitly in my previous comment.)

Unless this is handled by a different bug report, I'd therefore leave this one open for now.
Comment 9 Nate Graham 2018-01-17 15:02:55 UTC
Great, thanks for the update. Would you like to change the title accordingly, since printing to a real printer does work now?
Comment 10 Michael Weghorn 2018-01-17 15:07:52 UTC
(In reply to Nate Graham from comment #9)
> Great, thanks for the update. Would you like to change the title
> accordingly, since printing to a real printer does work now?

That sounds like a good idea. What about "Grayscale option ignored when generating print data for PDF document"?
(Note that I don't seem to have the permission to change the title myself, since I am not the reporter of the bug).
Comment 11 Nate Graham 2018-01-17 15:09:51 UTC
Sounds good!
Comment 12 Michael Weghorn 2018-02-13 21:48:06 UTC
*** Bug 390409 has been marked as a duplicate of this bug. ***
Comment 13 vasosergiou 2018-11-22 09:41:23 UTC
I am seeing this problem with colour and duplex printing on our Canon printer, on openSuse Leap 15. I need to make changes in the advanced settings before the changes I want are used.
Comment 14 Luigi Toscano 2018-11-22 10:45:28 UTC
(In reply to vasosergiou from comment #13)
> I am seeing this problem with colour and duplex printing on our Canon
> printer, on openSuse Leap 15. I need to make changes in the advanced
> settings before the changes I want are used.

As far as I know, openSUSE Leap 15 still uses Qt 5.9. Could you please check it? Also, it may be possible that openSUSE packagers backported some of the patches, but then it's up to them to check whether this is still valid.
Comment 15 vasosergiou 2018-11-24 12:48:11 UTC
I can confirm that openSuse Leap15 is using Qt 5.9.4. I guess I need to wait or upgrade to Tumbleweed
Comment 16 Justin Zobel 2023-01-18 02:41:21 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 17 Bug Janitor Service 2023-02-02 05:01:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 18 vasosergiou 2023-02-02 12:24:15 UTC
I am unable to check this bug easily as I don't have a pc with openSuse or even Linux installed anymore (have gone to FreeBSD). I'll see if I can test in a VM somewhere.
Comment 19 Bug Janitor Service 2023-02-17 03:48:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 20 Bug Janitor Service 2023-03-04 03:45:54 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!