Bug 63885 - printing more than one copy of a document is buggy
Summary: printing more than one copy of a document is buggy
Status: CLOSED WORKSFORME
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-08 09:12 UTC by Unknown
Modified: 2008-12-31 13:16 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 Rudolf Kollien 2003-09-08 09:12:59 UTC
Version:            (using KDE KDE 3.1.2)
Installed from:    SuSE RPMs
Compiler:          precompiled none
OS:          Linux

When printing multiple copies of a document the wrong (to high) number of copies are printed.

Selecting a copy number higher than 1 in the printing dialog you will get a multiple of the requested copy.

Printing a 2-page document with the option "collect" DISABLED and requesting 2 copies, the following is printed (by page number):

11221122

So there a 4 copies of each page. Requesting a copy of 3 prints 111222111222111222. It seems to result always in n*n copies in wrong order.


Printing the document with the option "collect" ENABLED and requesting 2 copies:

12121212

Also the wrong number of copies is printed (4 x p.1 and 4 x p.2). Requesting 3 copies prints n*n*n.

This happens on every app. (kate, kwrite and even acrobat reader with kprinter as print command) printing via kdeprint/kdeprinter.
 
Using SuSE Linux 8.1 on Intel
KDE 3.1.2 (SuSE RPMs from KDE.org)
cups-1.1.19-3 (as RPM from SuSE ftp server).
Comment 1 Stephan Kulow 2004-06-01 19:13:05 UTC
Replaced Rudolf.Kollien@medas.de with null@kde.org due to bounces by reporter
Comment 2 Matthias Kretz 2004-06-23 10:37:44 UTC
I have the same problem and can't get a hold of the bug by looking at the code. I'm using CUPS as print system.
Comment 3 Kurt Pfeifle 2007-01-13 03:58:28 UTC
There used to be a CUPS bug like that, in a specific version that I don't remember....

Should long be gone...
Comment 4 John Layt 2008-12-31 13:16:49 UTC
Closing old Resolved status bug.