I just upgraded Okular from the Applications 16.08.x version to the version from Applications 16.12.0. If I try to print a single-page PDF non-duplex, Okular still activates duplex printing, rotates the paper and prints on the backside. ("Duplex: none" is chosen in the print dialog.) This worked fine before and now gives me a big headache with my paper with pre-printed letterheads... :-/ My printer is a Brother DCP-7065DN, duplex printing works fine from the command line and in all other applications I tested (like Chromium, LibreOffice, Adobe Reader and previous Okular versions). Maybe related to #373133, which basically is a report of the opposite problem? In any case, this looks like as if there is definitely something messed up concerning duplex-printing in the new Okular release...
Very funny how this is exactly the reverse bug of https://bugs.kde.org/show_bug.cgi?id=373133 So at the same time only prints in duplex and never prints in duplex ^_^
Maybe Okular just fails to provide the required info to the printer driver which then prints using its default settings for duplex printing? This could explain the apparent contradiction...
Maybe. Though when I look at systemsettings' printer settings, duplex is actually off.
In order to analyse the problem further, it would be very helpful to have the PPD file of the printer in use. It is usually stored under '/etc/cups/ppd/<PRINTERNAME>.ppd'. In case it could be attached to this bug report, that might be very helpful.
I have had a look at the situation and have posted an idea about a possible cause in bug 373133 where the underlying cause might be the same: https://bugs.kde.org/show_bug.cgi?id=373133#c9 I would be very thankful in case somebody who is affected by the bug could test and give feedback whether my assumption there is true for their situation. (I do not own any of the mentioned printers by myself...)
Note also that the "Advanced" options tab has been reintroduced for the current development version of Qt 5 [1]. Also, the problem with duplex options being set at different places (which was present in Qt 4) has been fixed [2], so I'd expect that your problem should probably be solved with those Qt upstream changes (will be part of the upcoming Qt 5.11). [1] https://codereview.qt-project.org/#/c/213391/ [2] https://codereview.qt-project.org/#/c/215131/
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!
Seems to be fixed in current Okular's.