Description of problem: evince is not printing duplex page even if duplexNoThumble (LongEdge) is set on the printer. Version-Release number of selected component (if applicable): $ rpm -q evince evince-3.10.3-1.fc20.x86_64 How reproducible: Steps to Reproduce: 1.create a two page pdf 2.print on duplex capable printer (Brother HL-5250DN) 3. Actual results: first page on first file, second page on second file Expected results: both pages on first file Additional info: Same thing happens in Fedora 19 x86. Same thing happens in Fedora 20 with LibreOffice-Writer xpdf is able to print correctly on both versions of Fedora: $ rpm -q xpdf xpdf-3.03-8.fc20.x86_64
I also see this bug. Fedora 19 x86_64 Printer is a Brother HL-5340D. Driver is 'Brother HL-5350DN BR-Script3'. Changing duplex settings in 'Gnome settings' or system-config-printer make no difference to the ability to be able to print duplex from Evince or Libreoffice. No duplex printing occurs with any combination of settings. Name : evince Arch : x86_64 Version : 3.8.3 Release : 2.fc19 Name : libreoffice Arch : x86_64 Epoch : 1 Version : 4.1.4.2 Release : 1.fc19 NB - Printing duplex from KDE Okular is good.
Forgot to mention - duplex printing worked fine from Evince in Fedora 17.
I'm also seeing this bug on F19. I can't print duplex from Evince. This used to work in F18 and I think it might have worked for a while in F19, but I'm less certain about that, not sure exactly when it stopped working. Printer is Brother MFC-9840CDW with the "Brother MFC-9840CDW BR-Script3" driver enabled. FWIW this printer also serves a Windows box where I have the Brother Admin console installed. I verified the printer has duplex mode enabled in the printer. I also verified Adobe Reader on Windows can print duplex to this printer. The problem seems to be specific to Fedora.
I have a Brother HL-5270DN printer and I can confirm all these observerations regarding duplex printing. It did work fine with F18, but I saw the problem also with F19 and than F20. In some weeks ago (April?) duplex magically worked again. Some updates later -- nada, same symptoms.
I installed the pdftops program from poppler 0.26 and duplex printing works from Evince and LibreOffice. Maybe the problem is related to #1068896 and https://bugs.freedesktop.org/show_bug.cgi?id=72312
Propably I have the same issue. I have an HP 4700DN duplex capable printer and duplex printing used to work fine using the recommended postscript driver. However recently duplex printing stopped working, on any application that uses the standard gnome print dialog (such as evince & firefox). One temporary workaround is to remove the postscript printer driver and use the pcl3 one. Afterwards duplex printing works fine, but the pcl3 driver has less features than the postscript one. If poppler & poppler-utils 0.26 fix the issue, are they going to be backported to fedora 20? As far as I know these versions are for fedora 21 and they are not fedora 20 compatible. In my opinion this is a major bug for people who need duplex printing. Waiting for fedora 21, for this issue to be fixed, is too long. This issue must be fixed in fedora 20.
Another workaround is to run the following command as root: lpadmin -p PrinterName -o pdftops-renderer-default=gs Substitute PrinterName with the name of your printer, in my case it's HP-Color-LaserJet-4700.
have not tested it recently, but it may be that the printer settings from applications are ignored, and are used the ones in gnome-control-center instead. there you can (probably) fix the paper size, also. can anyone confirm it?
(In reply to cornel panceac from comment #8) In my case the page size is properly set (A4) in gnome-control-center and in the application, but that didn't help at all. Running lpadmin -p PrinterName -o pdftops-renderer-default=gs fixed the issue (I guess it's a temporary workaround).
i tried to say you should set the duplex printing, in gnome-control-center. and also, the paper size.
(In reply to cornel panceac from comment #10) Duplex was also set/enabled in gnome-control-center and in the application (and in the printer configuration), but that didn't help.
re comment #8. No it's not a problem with preference settings, duplex is set in both the printer defaults and in the app print dialog.
I too have this problem with a USB-connected Brother HL5150d printer. No settings seemed to get evince to print duplex (the printer went through the motions of printing both sides, but one was always blank). The kludge that Panormitis Petrou mentioned comment 9 worked for me. Not a good solution. Please backport the fixed version of pdftops to Fedora 20.
I spoke too quickly. Although the duplex problem went away with the pdftops-renderer-default=gs kludge, scanned images printed in a distorted form. I have no idea why. I've built a new set of poppler RPMs, based on poppler-0.24.4 + selected commits that were claimed to address https://bugs.freedesktop.org/show_bug.cgi?id=72312 I had to lie about the version number because otherwise the libpopper.so would not satisfy requirements of other packages. I don't get this: the convention used to be that version x.y+1 would satisfy requirements for x.y. The resulting RPMs, installed via rpm -Fv, seem to work and to fix the duplex problem. See <http://copr.fedoraproject.org/coprs/hugh/poppler-fix-f20/>. This is an experiment
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
I still see this in Fedora 23. evince-3.18.2-3.fc23.x86_64 poppler-0.34.0-1.fc23.x86_64 Printer is Brother-MFC-9340CDW From lpoptions -l: BRDuplex/Two-Sided: DuplexTumble *DuplexNoTumble None
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.