Generic PCL6/pxlcolor PPD causes severe delays when printing multiple copies at 1200 dpi

Open
#66 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux
Domain
backend

Research direction

Start by locating the generic PCL 6/PCL XL pxlcolor PPD and its filter definitions, then trace how copy counts reach the direct PDF-to-Foomatic path. Check whether the PPD can advertise hardware copies and compare generated output for multiple-copy jobs. Done means copy counts work through the supported path and the printer can render the page once for consecutive copies; confirm behavior across printer models.

Written by the indexing model from the issue text.

Description

Environment

  • Printer: OKI C532dn
  • Connection: socket://192.168.0.8:9100
  • CUPS: 2.4.7-1.2ubuntu7.14
  • libcupsfilters: 2.0.0-0ubuntu7.2
  • libppd: 2.0.0-0ubuntu4.1
  • Driver: Generic PCL 6/PCL XL Printer Foomatic/pxlcolor

Problem

When printing multiple copies of a graphics-intensive, single-page PDF at 1200 × 1200 dpi, the printer pauses for processing between every copy.

At 600 × 600 dpi, the same behavior is not visibly problematic.

The generated PCL XL data for one page is approximately 178 MiB.

Cause identified

The generated PPD contains:

*cupsManualCopies: True
*cupsFilter: "application/vnd.cups-postscript 100 foomatic-rip"
*cupsFilter: "application/vnd.cups-pdf 0 foomatic-rip"

CUPS expands multiple copies into separate pages before rendering.

Changing cupsManualCopies to False prevents this expansion, but the direct PDF-to-Foomatic path then produces only one physical copy when multiple copies are requested.

Working workaround

  • Set cupsManualCopies: False
  • Remove the direct application/vnd.cups-pdf filter entry
  • Retain the PostScript-to-Foomatic filter
  • Set the appropriate color-mode defaults

With this configuration, two copies are printed consecutively without processing delays, at 1200 × 1200 dpi in color.

Observed test results

  • Original configuration, 2 copies: PDF-to-PostScript output contains 2 pages, approximately 119 MiB
  • Modified PPD, 2 copies: PDF-to-PostScript output contains 1 page with %RBINumCopies: 2, approximately 60 MiB
  • Final PCL XL output: approximately 178 MiB, rendered once
  • Physical printer test: 2 copies printed without processing delay

Request

Please investigate whether the generic pxlcolor PPD could support hardware copy generation where available, and whether copy-count propagation in the direct PDF-to-Foomatic filter path can be corrected.

AI assistance disclosure

This issue was investigated with the assistance of ChatGPT.

I encountered the problem on my own printer and personally executed all diagnostic commands, printing tests, and configuration changes. All reported measurements and printing results were obtained from my actual system.

ChatGPT assisted with troubleshooting, interpreting the results, developing the workaround, and preparing this report.

The workaround has been verified on my OKI C532dn, but has not been tested on other printer models.

Dominant language
HTML
Stars
14
Forks
26
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenPrinting/foomatic-db

All issues in OpenPrinting/foomatic-db

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.