+++ This bug was initially created as a clone of Bug #768811 +++ Description of problem: Printing a landscape document prints in portrait. Also applies to the brochure option. Preview is correct. Version-Release number of selected component (if applicable): 3.4.4 How reproducible: Happens every time. Steps to Reproduce: 1.Select a document that has the page orientation set to Landscape 2.Go to Print 3. Check Properties are set to Landscape and if applicable go to Page Layout and check Brochure is selected 4. Click Print Actual results: Document prints in portrait showing the left hand part of the document with the right side cut off. Expected results: Output to be landscape Additional info: Paper size is A4, Printer is Brother HL-5340D Laser with duplex. Same document prints as expected from Fedora 15 and Libreoffice 3.3.4.1 --- Additional comment from Till Kamppeter on 2013-12-04 14:53:03 CET --- The real problem is in Poppler, it is that "pdftops -origpagesizes" does not take into account the rotation fields of the input PDF pages. If pdftopdf encounters a landscape-oriented page and the printer takes paper only short-edge-first (portrait), pdftopdf rotates the page by setting its rotation field (increment value by 90 degrees), which is much more efficient than rotating all the content of the page. All viewers (evince, gs, gv) take the rotation field into account and show the pages correctly rotated. In "pdftops -origpagesizes" this was forgotten and so in its output all pages are unrotated, leading to the wrong printouts mentioned by the reporter of this bug. Dropping "-origpagesizes" in the pdftops filter of cups-filters is only a workaround, not a fix. I have fixed Poppler with a patch. See https://bugs.freedesktop.org/show_bug.cgi?id=72312 Therefore I have not taken the patch attached to this bug upstream into cups-filters. cups-filters I have modified to always use "-origpagesizes" now as it works correctly with my Poppler fix. This I have done in cups-filters upstream BZR rev. 7131. Please apply my patch of the Poppler bug report to your Poppler package and also apply the BZR rev. 7131 patch to the cups-filters package. Please reopen this bug and assign it to both cups-filters and poppler. --- Additional comment from Bill McGonigle on 2013-12-04 17:44:13 CET --- Nice work, Till! We'll probably need two new bugs here, one to track the upstream poppler release with this patch in it, and then a cups-filter bug to revert the change here, when that poppler release comes downstream to Fedora, the latter bug depending on the former.
Marek, would it be possible to backport https://bugs.freedesktop.org/show_bug.cgi?id=72312 to Fedora 19 + 20 ?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.