Bug 60136

Summary: Printer concatenates multiple copies as one causing problems on duplex printers
Product: [Unmaintained] kdeprint Reporter: Vladimir Vuksan <vvuksan>
Component: generalAssignee: KDEPrint Devel Mailinglist <kde-print-devel>
Status: CLOSED NOT A BUG    
Severity: normal CC: jlayt
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Vladimir Vuksan 2003-06-20 18:14:34 UTC 
Version:            (using KDE KDE 3.1)
Installed from:    RedHat RPMs

If you try and print multiple copies of a document to a duplex printer kprinter will concatenate the job together causing problems on jobs that have odd number of pages ie. I have a print job that is 3 pages long and I am printing 2 copies of a document. Last page of first copy and first page of second copy will be printed on the same sheet of paper back to back.
Comment 1 Cristian Tibirna 2005-08-22 20:58:08 UTC 
UNCONFIRMED (batch reassigning messed this)
Comment 2 Cristian Tibirna 2005-09-22 07:39:38 UTC 
What printing system?
Comment 3 Vladimir Vuksan 2005-10-20 19:41:33 UTC 
THis is using CUPS.

Vladimir
Comment 4 Cristian Tibirna 2005-10-24 14:05:32 UTC 
Try please to print a test 2 copies of a document of odd number of pages using the lpr(1) command from the CUPS package. Does it still print the last page of the first copy and the first page of the second on the same sheet?
Comment 5 Kurt Pfeifle 2007-01-08 22:39:20 UTC 
Vladimir,

can you tell the version of CUPS you are using? I know an early version of CUPS showed this behavior (for me it was a feature, Mike Sweet thought of it as a bug, so it may be changed now in CUPS 1.2.7).

Also, can you please try

  lp -d yourprinter /path/to/file1-with-odd-no-of-pages /path/to/2nd-file

and see if this is still the case?

(And if it is, it is a CUPS thingie [bug or feature]).

In any case, I will close this bug report now, because

 (a) INVALID (it is not KDEPrint's responsibility)
 (b) timeout -- no feedback since Cristian's request (2005-10-24 14:05)

Cheers,
Kurt
Comment 6 John Layt 2008-12-31 13:12:32 UTC 
Closing old Resolved status bug.