[okular] [Bug 373133] 16.12.0 Okular duplex printing on but no duplex printing done

[Michael Weghorn]

https://bugs.kde.org/show_bug.cgi?id=373133

--- Comment #16 from Michael Weghorn <m.weghorn at posteo.de> ---
Thank you for providing more information.

I think that the problem (or at least a part of it) is that the PPD uses the
vendor-specific "BRDuplex" keyword instead of the standardized "Duplex" one and
the printer possibly ignores the "Duplex" options in the modified PPD.

The log file shows that the option "sides=one-sided" is even present for the
case where you chose "long sided" in the Okular print dialog (which in my
expectation should have resulted in "sides=two-sided-long-edge"). From a quick
glance, this might be because Qt only handles the "Duplex" keyword to decide
whether a printer supports duplex.

When I try with the modified PPD file, I can see that the option
"sides=two-sided-long-edge" is set as expected in the CUPS log (with no real
printer available, I don't get any output however). Since you said that this
does not work either, the proprietary Brother printer driver ignores it as it
only handles its own vendor-specific option...

Are there other applications where setting the duplex option in the print
dialog does work as expected?
(I just came across
https://askubuntu.com/questions/766471/non-standard-keywords-in-postscript-printer-driver-ppd-break-integration-with)
where somebody else describes problems with the Brother-specific keywords.)

Is it possible that you had previously changed the system-wide setting for the
duplex option and this is now back to the default since you used the original
PPD file again (since duplex is deactivated again)?

Is duplex enabled again for the printouts when you run 'lpoptions -p
<YOUR_PRINTER_NAME> -o BRDuplex=DuplexNoTumble' (and disabled after running
'lpoptions -p <NAME_OF_YOUR_PRINTER> -o BRDuplex=None')?
(This writes the respective value to '$HOME/.cups/lpoptions' and is basically
what my assumption in comment 9 was, but there seems to be more to it in
conjunction with the vendor-specific keyword.)

-- 
You are receiving this mail because:
You are the assignee for the bug.