Can only print one copy via LPR




8 years ago
7 years ago


(Reporter: mozilla, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2011-2-25])



8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6

  Running Firefox 3.6 under Debian Lenny (GTK 2.12.12). I can not print multiple copies of any Web page via LPR. Setting the number of copies desired to any value produces one copy.

    The postscript that is generated by Firefox does not contain a "NumCopies" line to specify the desired number of copies and the "Pages" line shows the page count of a single copy.

  I am not sure if Firefox should be using the -n switch for LPR (it isn't) or sending a single Postscript file that has the information about multiple copies, which seems likely.

  Printing to a file also creates a single-copy Postscript file.

  Printing works fine if printing to CUPS.

Reproducible: Always

Steps to Reproduce:
1. Disable Cups
2. Print a Web page via LPR (or to a file)
3. Get one copy from printer.

Actual Results:  
One copy of printed page is produced by printer

Expected Results:  
Multiple copies (whatever value was set by the user) of printed page should be produced by the printer.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
Also, ensure you update all your plugins (Flash, Reader, java, quicktime, etc) to the latest version available on the vendor's website.
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is
far gone. If the reporter can still see this issue, Please retest with Firefox
3.6.x or later and a new profile
( Then please remove the
closeme tag in the whiteboard, mark the bug against the proper version and
comment on the bug.
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.