Created attachment 1375668 [details] Dialog seen when printing from okular Description of problem: ======================= > Okular 1.2.1 > Konica Minolta Bizhub C224e printer (driver KONICA MINOLTA C250 PS(P)) When printing from Okular, the print Dialog has an "Options" element through which one can select two sided printing and grayscale. These values are not honored. ( Another example, when printing from LibreOffice: You can select "Properties" on the "Printer" For some reason the "Duplex" property cannot be select (mysterious!) But you can set the "Duplex" property to "on" in another screen ...although there is no possibility to switch to grayscale ) Version-Release number of selected component (if applicable): ============================================================= Okular 1.2.1 cups-2.2.4-6.fc27.x86_64 How reproducible: ================== Always
Created attachment 1375669 [details] Dialogs seen when printing from LibreOffice
Created attachment 1375752 [details] Dialog seen when printing from Firefox 57.0.1 Incidentally, two-sided grayscale also works from Firefox (which brings yet another menu to the table)
Tried to print with evince, which works. evince also uses the same dialog as Firefox, I see.
Fwiw, okular essentially runs lpr by hand to do printing ... Looking at the code, I see if duplexing is selected as you did, it uses lpr -o sides=two-sided-long-edge ... Can you check if envoking that by hand makes duplexing work as expected or not? (If not, this may be a cups/lpr bug)
Hi, I tried to print pure ASCII with lpr -P Printer109 -o sides=two-sided-long-edge Extract.txt but two-sided ain't working in that configuration. Interesting... how to debug?
Assuming your printer and driver setup supports duplexing, this is a cups issue (adjusting summary and assigning to cups)
Hi David, would you mind telling me which driver are you using and attach ppd file for this printer if possible? Are you able to reproduce this issue with 'lp' command and with other type of files (like pdf)? e.g. $ lp -d your_printer -o sides=two-sided-long-edge file.pdf
ppd files are under /etc/cups/ppd directory.
Okay, note thw following: 1) The printer selected is a (Konica Minolat Bizhub) "C250" whereas the actual printer is a "C223e" (it seems they are similar enough; there is no separate file for C250. 2) Selection was done through the KDE Printer dialog (see attached screenshot) 3) The PPD file in use is /etc/cups/ppd/Printer109.ppd (attached). It is called "109" because the printer is at address X.X.X.109 That file is the same as /usr/share/foomatic/db/source/PPD/KONICA_MINOLTA/KOC250UX.ppd.gz except for the values of: *DefaultDuplexUnit: True *DefaultPageSize: A4 *DefaultPageRegion: A4 *DefaultPaperDimension: A4 *DefaultImageableArea: A4 4) The PPD file is also the same as /opt/OpenPrinting-KONICA_MINOLTA/ppds/KONICA_MINOLTA/KONICA_MINOLTA-C250_PS_P-Postscript-KONICA_MINOLTA-en.ppd.gz from package "openprinting-ppds-postscript-konica-minolta-20130226-1lsb3.2.noarch" which can be downloaded from the Konica Minolta website Except for the NickName: < *NickName: "KONICA MINOLTA C250 PS(P)" --- > *NickName: "KONICA MINOLTA C250 PS/P , Postscript-KONICA_MINOLTA 20130226 (OpenPrinting LSB 3.2)" Test printing ------------- In both cases, the output is single-sided: lp -d Printer109 -o sides=two-sided-long-edge TestText.pdf lp -d Printer109 -o sides=two-sided-long-edge TestText.txt Can one log what CUPS does when one prints via "lp" as opposed to through the print dialog of evince for example?
Created attachment 1381351 [details] KDE Printer dialog screenshot
Created attachment 1381352 [details] "KONICA MINOLTA C250 PS(P)" ppd file in use
(In reply to David Tonhofer from comment #9) > > Can one log what CUPS does when one prints via "lp" as opposed to through > the print dialog of evince for example? Yes, we can see that from logs. David, would you mind doing similar thing as in #1536621 - that means capturing the logs when option works (printing from evince) and when doesn't (printing by lp) and creating diff of it as in #1536621 comment #12?
*** Bug 1552353 has been marked as a duplicate of this bug. ***
David, I tried to reproduce the issue when printing from okular and firefox - both worked well, so I think the issue might be in ppd file or your printer uses different filters for printing.
I think something similar occurred in the past: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781253 and ghostscript was at fault there... we will see what filters are used during good and bad print. If it is the case, setting: $ lpadmin -p <printer> -o pdftops-renderer-default=pdftops should help. Then we can gather other debug information.
Created attachment 1405889 [details] PPD file from bug #1552353 This is my PPD file as requested from bug #1552353
Thank you, John! Your ppd file has same Duplex section as mine, so I think the problem will be in filters or in ghostscript itself. My printer uses pdftopdf filter, so yours can use something else... Would you mind attaching diff of two logs - successful and unsuccessful - as David did in #1536621, and trying > > $ lpadmin -p <printer> -o pdftops-renderer-default=pdftops > , if it helps?
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I noticed this is still needinfo on my part. Unfortunately I have no longer access to the hardware.