Bug 472698 - Duplex printing does not work correctly
Summary: Duplex printing does not work correctly
Keywords:
Status: CLOSED DUPLICATE of bug 439937
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: evince
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Kristian Høgsberg
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-23 19:27 UTC by Yulia Kopkova
Modified: 2009-07-23 14:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-23 14:04:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yulia Kopkova 2008-11-23 19:27:48 UTC
Description of problem:
When printing multiple copies of a document in duplex mode, the each page is printed on the both sides of sheet.

Version-Release number of selected component (if applicable):
evince-0.6.0-8.el5

How reproducible:
100%

Steps to Reproduce:
1.Create a three page document in OpenOffice.org Writer
2.Export to a PDF, call it test.pdf
3.Open PDF in Evince
4.Run printing dialog
5.Select number of copies 2
6.Set "Collate" option
7.Select Page Setup->Layout->Two-sided: Long Edge
8.Print
  
Actual results:
Six sheets of paper, 1-1, 2-2, 3-3, 3-3, 2-2, 1-1

Expected results:
Four sheets of paper, 1-2 3-blank 1-2 3-blank


Additional info:

Comment 1 RHEL Program Management 2009-03-26 17:19:49 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 4 Marek Kašík 2009-07-23 14:04:30 UTC
This bug is caused by the same problem as the one in the bug #439937.
  => resolving as DUPLICATE

Marek

*** This bug has been marked as a duplicate of bug 439937 ***


Note You need to log in before you can comment on or make changes to this bug.