PostScript files print only PJL headers, no file content

Bug #1005857 reported by oddhack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
New
Undecided
Unassigned

Bug Description

Printing a PostScript file (a valid one that looks correct in e.g. ghostview) just generates two pages of output, neither of which is a rendered representation of the PostScript I printed. The first page contains fragments of PJL looking like this (each line appears to be end with a newline but no carriage return, though that's hard to show in a proportional font):

"@PJL SET MEDIATYPE=REGULAR
                                                             @PJL SET SOURCETRAY=AUTO
                                                                                                                      @PJL SET RESOLUTION=600
                                                                                                                                                                          @PJL SET"
(runs off right page edge at this point). I'd speculate there's more PJL after this that's completely off the page edge, but there's no way for me to tell.

The second page is completely blank.

Printing a PDF file, for example printing a few lines of text from a libreoffice text document, works properly.

I paused the print queue and looked in /var/spool/cups after printing. The "d<job#>" file corresponding to the PostScript print job contained exactly the .ps file I printed, with no trace of embedded PJL. I also turned up the cupsd.conf logging level and am attaching the resulting error_log - job 13 is the unsuccessfully printed PostScript file and job 14 is the successfully printed PDF. I don't see anything obviously wonky here but I am far from an expert at deciphering CUPS activity.

This system and printer were running under Ubuntu 10.04 until a few days ago, when I did an upgrade to 12.04 from a flash drive, and printing of PostScript files worked correctly under 10.04 and the corresponding version of CUPS. I had not configured the printer in any special way under 10.04, either, so the behavior change appears to be localized to the CUPS version that came with 12.04.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cups 1.5.2-9ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Tue May 29 04:14:32 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
Lpstat:
 WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-4x9LQO/pkcs11: No such file or directory
 device for HL-1450-series: usb://Brother/HL-1450%20series?serial=F1J151107
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7549
Papersize: letter
PpdFiles: HL-1450-series: Brother HL-1450 Foomatic/hl1250 (recommended)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae root=UUID=64f3c471-1216-423e-a99c-8c7d66fcc976 ro quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V8.3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 785GTM-E45 (MS-7549)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.3:bd01/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7549:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785GTM-E45(MS-7549):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7549
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
modified.conffile..etc.cups.cupsd.conf: [modified]
mtime.conffile..etc.cups.cupsd.conf: 2012-05-28T19:42:58.172245

Revision history for this message
oddhack (developer-oddhack) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.