Bug 128947 - Setting Page Set Odd or Even with more than 1 copies results in printing twice as much pages as wanted
Summary: Setting Page Set Odd or Even with more than 1 copies results in printing twic...
Status: CLOSED WORKSFORME
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-10 15:47 UTC by Tobias Klein
Modified: 2008-12-31 20:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Klein 2006-06-10 15:47:54 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Compiled From Sources
Compiler:          GCC 3.3.5 
OS:                Linux

The following setup leads to the problem that kprinter prints twice as much pages as wanted:

Document with two pages
Page set: Even/odd
Copies: more than one

KPrinter then prints 2*number of copies - twice as much as wanted.
Comment 1 Kurt Pfeifle 2007-01-09 04:40:53 UTC
Tobias,

can you re-check with KDE 3.5.5 if you still see this bug? Which type of document did you print, from which application?

If yes, then please tell...

  ...your CUPS version,
  ...does this only happen with specific document types, such as PDF?
  ...if printing a 3-page document 3 times results in 9 copies (3*3),
  ...if printing from the commandline (purely CUPS) also shows this error

For the commandline tests use this syntax:

  lp -d your_printer_name -n 3 -o page-set=odd /path/to/3-page-document.pdf
  lp -d your_printer_name -n 3 -o page-set=odd /path/to/3-page-textfile.txt
  lp -d your_printer_name -n 3 -o page-set=odd /path/to/3-page-psfile.ps

If I don't hear from you until Feb 1, 2007, I'll assume the problem has gone and close this bug report.

Cheers, 
Kurt
Comment 2 Camilla Boemann 2007-05-21 13:32:57 UTC
As Feb 1 has passed and I don't see the problem I'll close it
Comment 3 John Layt 2008-12-31 20:05:23 UTC
Closing old Resolved status bug.