@ahasenak, I have uploaded an SRU for this bug for Lunar right now. As
soon as it gets approved, please test it as described in the initial
description (there is an option to do it without an affected printer)
and report back here.

I will not upload an SRU for Kinetic, as this version is already EOL.

** Also affects: okular (Ubuntu Lunar)
   Importance: Undecided
       Status: New

** Also affects: cups (Ubuntu Lunar)
   Importance: Undecided
       Status: New

** Also affects: atril (Ubuntu Lunar)
   Importance: Undecided
       Status: New

** No longer affects: atril (Ubuntu Lunar)

** No longer affects: okular (Ubuntu Lunar)

** Changed in: cups (Ubuntu Lunar)
   Importance: Undecided => High

** Changed in: cups (Ubuntu Lunar)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed
Status in cups source package in Lunar:
  In Progress

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

      lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

      lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

      lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

      sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

      FiileDevice Yes

  and start CUPS again:

      sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

      lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

      @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

      @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to