Pdf file silently fails to print

Thank you for taking the time to report this bug (and including a test document!) and helping to make Ubuntu better. I've tried recreating this bug report using evince version 2.26.0-0ubuntu1 in Jaunty Jackalope and I was able to print the document successfully. Could you possibly try it with a Live CD of Jaunty? Thanks in advance.

Two test cases tried with my HP DeskJet 952c with evince 2.26.0-0ubuntu1 and cups 1.3.9-15:

Printing the whole document:
Fails silently, however the printer gives a flashing amber LED indicating an error. When I press the "feed paper" button it prints a page with the line "Unrecoverable error: rangecheck in .putdeviceprops" on it.

Printing just the first page:
It fails UNsilently for me.

I get a "Print Error" dialog that just says "There was a problem processing document Presentation_for_Brown_Bag_Jena_3_March_2009.pdf"

Then, when I press the "feed paper" button it again prints that "Unrecoverable error" message.

Architecture: amd64
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
DistroRelease: Ubuntu 9.04
Lpstat: device for DESKJET_950C: hp:/usb/DeskJet_950C?serial=MY9AR110XWJP
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: cups 1.3.9-15
PackageArchitecture: amd64
Papersize: letter
PpdFiles: DESKJET_950C: HP DeskJet 950C Foomatic/cdj550
ProcCmdLine: root=UUID=77e7add8-df1a-47df-9dab-27d08d56f63c ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-11.35-generic
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Can you please do the following:

cupsctl LogLevel=debug
cancel -a

Then print the failed job again and as soon as the job gets into "Stopped" state (or disappears) do

sudo cp /var/log/cups/error_log ~
sudo chmod 777 ~/error_log

and attach ~/error_log to this bug report.

Do this for both cases of problems (full document, first page).

Thanks in advance.

Attaching the logs.

First page only:
Silently Failed. (just the blinking amber LED associated with the "feed paper" button).

Full Document:
Failed with the dialog I referenced above.

David:

Did you also upgrade to Jaunty from Intrepid? (not do a clean install)

I just deleted my printer (from the printer configuration tool in System->Administration) and re-added it; now printing works. I just printed the first page of your pdf and 17 pages of another pdf.

gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -r300x300 -sDEVICE=cdj550 -dBitsPerPixel=1 -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -dDepletion=2 -sOutputFile=- /usr/share/system-config-printer/testpage-a4.ps > out.prn

does not output the expected PCL but

Unrecoverable error: rangecheck in .putdeviceprops

This happens already before the input file gets read. You get the same result if the input file is neither PostScript nor PDF.

gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -r300x300 -sDEVICE=cdj550 -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -dDepletion=2 -sOutputFile=- /usr/share/system-config-printer/testpage-a4.ps > out.prn

Leads to PCL output. Here only the "-dBitsPerPixel=1" was removed. Using "-dBitsPerPixel=3", "-dBitsPerPixel=8", "-dBitsPerPixel=16", "-dBitsPerPixel=24", or "-dBitsPerPixel=32" instead also work. Seems to be a bug in foomatic-db generating an invalid command line. Moving to foomatic-db ...

Greg Grossmeier, your re-creation of the print queue has probably chosen another (better) driver for your printer (please tell which one). In general, who has an HP inkjet and gets automatically assigned the "cdj550" driver, please try changing manually (with system-config-printer) to a better one, like HPLIP/HPIJS. Please tell if this happens for you.

For anyone who uses the "cdj550" driver, please choose anything else than "Black and White" for the "Color Mode" option. "Black and White" does not work.

Removed black-and-white mode fropm the "cdj550" driver in foomatic-db upstream.

This bug was fixed in the package foomatic-db - 20090617-0ubuntu1

---------------
foomatic-db (20090617-0ubuntu1) karmic; urgency=low

  * New upstream release
    - Many new printer models added (Fixes: LP: #10871, LP: #83960,
      LP: #114681, LP: #121060, LP: #258058, LP: #273975, LP: #343444,
      LP: #371737).
    - More user-friendly UI strings for the "Print Quality" option in some
      Brother PPD files (LP: #141487).
    - Replaced broken PPD for the Kyocera FS-9100DN by the one for the
      FS-9120DN (LP: #344691).
    - Added "*cupsFilter:" lines to all PCL-XL PPD files from Ricoh and OEM
      so that they accept PDF as input format. This assures that always the
      most straightforward CUPS filter chain gets used and interferences
      between filters (like LP: #361772) get avoided.
    - Removed "Black and White" Color Mode (1 bit per pixel) from the
      "cdj550" driver. This mode is not supported by the driver (LP: #337133).
    - DesignJet driver assignement fixes, new "cdnj500" driver.
    - Correction of auto-detection strings.
    - Addition of CUPS custom option definitions to the PPDs from Ricoh
      family and OEM.
    - New "pxldpl" driver entry for the Dell 3010cn and Dell DPL printers
      in general.
  * Merge from debian unstable, remaining changes:
    - Driver entries removed for drivers which are not shipped by Ubuntu
    - Fixed manufacturer-supplied PPDs: "*CloseUI <option>" ->
      "*CloseUI: <option>", "*1284DeviceId" -> "*1284DeviceID".
    - openprinting-ppds-extra package with PPDs from Ricoh family and OEM
      and non-English PPDs from Kyocera
    - Linked PPD files with Foomatic database, so that links in the Foomatic
      XML files keep working.
    - Removed link into /usr/share/cups/model, it makes PPDs appearing
      twice.
    - debian/patches/bjc600-bjc800.patch: Removed workaround for Ghostscript
      crashing when feeding bjc600/bjc800 drivers with PDF. The Ghostscript
      shipped by Ubuntu is fixed.
    - foomatic-filters-ppds discontinued upstream, updated debian/control
      appropriately.
    - foomatic-db does not make sense without foomatic-db-engine and
      foomatic-filters, made the Recommends: a Depends:.

 -- Till Kamppeter <email address hidden> Wed, 17 Jun 2009 23:34:49 +0200