Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer

Bug #1157814 reported by Jeremy Bícha
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cups-filters (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This bug was also 'reported' at http://askubuntu.com/q/231355/1579

Xerox WorkCentre 7120

1. Download the printer model package from http://www.support.xerox.com/support/workcentre-7120/downloads/enus.html?operatingSystem=linux and extract the tarball. The version I used is 2010_10_15.
2. Open system-config-printer and click Add
3. Select Network Printer>AppSocket/HP JetDirect
4. Enter the printer's IP address and click Forward
5. Click Provide PPD and select ppd/xr_WorkCentre7120.ppd where you extracted the printer package. (I'm also attaching the ppd to this bug report)
6. Finish the rest of the add printer wizard (the defaults are fine) and click Print a Test Page

This works in Ubuntu 12.04 but in Ubuntu 12.10 and 13.04, the printer prints a page with this text:

ERROR:
invalidaccess
OFFENDING COMMAND:
def
STACK:
--nostringval--
/pagesave

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: cups-filters 1.0.30-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
Date: Wed Mar 20 11:54:51 2013
Lpstat:
 device for Epson-Stylus-Photo-RX595: bluetooth://001BDC0F40F8
 device for MP150: usb://Canon/MP150?serial=D25C1E&interface=1
 device for Xerox-WorkCentre-7120: socket://10.99.8.15:9100
 device for Xerox-WorkCentre-7228: socket://10.99.8.15:9100
MachineType: TOSHIBA Satellite L745
MarkForUpload: True
Papersize: letter
PpdFiles:
 MP150: Canon PIXMA MP150 - CUPS+Gutenprint v5.2.9
 Xerox-WorkCentre-7228: Xerox WorkCentre 7228 Foomatic/Postscript
 Xerox-WorkCentre-7120: Xerox WorkCentre 7120
 Epson-Stylus-Photo-RX595: Epson Stylus Photo RX595, Epson Inkjet Printer Driver (ESC/P-R) for Linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=da074346-bf87-4cf5-a9ec-8589cb501c4e ro quiet splash usbcore.autosuspend=-1 vt.handoff=7
SourcePackage: cups-filters
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L745
dmi.product.version: PSK0YU-05R02G
dmi.sys.vendor: TOSHIBA

Revision history for this message
Jeremy Bícha (jbicha) wrote :
description: updated
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Chris, can you help here? It seems again to be a PS printer with interpreter bug.

Revision history for this message
cliddell (cjl) wrote :

Till,

I believe we've been through enough of these that you should know the basic groundwork required before I can really do anything.

To start with, try the "uncompressed" CUPS option, and if that doesn't work, then gather the (preferably uncompressed) Postscript that is being sent to the printer to attach to this bug.

Also, please include the instructions on how to send PS data direct to the printer (both netcat and the "normal" method).

Revision history for this message
cliddell (cjl) wrote :

Jeremy,

Whilst we will investigate this, we are confident that the Postscript being emitted by Ghostscript is valid and correct, based on our own inspection of the Postscript code, and since it works correctly on a large number of devices.

Given that, it seems almost certain that there is a bug in the Postscript implementation on this printer.

As I said, we'll investigate, and hopefully find a workaround, but I would *STRONGLY* urge you, once Till posts instructions on how to gather the Postscript being sent to the printer, to report the problem to Xerox (including the problematic Postscript file in your report). On a printer of this spec and cost, there is no excuse for the Postscript interpreter being broken.

I feel quite strongly on this: if Ghostscript fails to interpret valid Postscript or PDF (and even many, many invalid PDFs!) we are expected/obligated to fix Ghostscript - we would be berated heavily for suggesting that the producer be changed to work around our bug. I don't see why bugs in other consumers be treated differently.

Chris

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Chris, I have posted instructions on

https://wiki.ubuntu.com/DebuggingPrintingProblems

now. See the sections

PostScript (PDF) printer chokes on the PostScript (PDF) coming from Ubuntu

and

Sending a file to the printer unfiltered

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Jeremy, can you follow the instructions in section

PostScript (PDF) printer chokes on the PostScript (PDF) coming from Ubuntu

on

https://wiki.ubuntu.com/DebuggingPrintingProblems

and report your results/attach the files here? Thanks.

Changed in cups-filters (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Sending the raw PDF straight to the printer queue worked.

cupsdisable Xerox-WorkCentre-7120
( print basic document from gedit )
sudo cp /var/spool/cups/d00008-001 test-printout
cupsenable Xerox-WorkCentre-7120
( printer prints error message)
sudo chmod 777 test-printout
lp -d Xerox-WorkCentre-7120 -oraw test-printout

Since this is different output (success instead of failure) on step 9 of the Printer chokes on output from Ubuntu instructions, I'll stop here because it's not clear what you want me to try next.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Sorry about the extra noise in this log from the other printers I have "added" to this computer but not enabled. Let me know if you need me to delete those printers and run the logs again.

Revision history for this message
cliddell (cjl) wrote :

Jeremy,

Your next step should be to try doing:
lpadmin -p <printer> -o psdebug=true

where "<printer>" is the name of the Xerox print queue, and try printing normally.

If that still gives the error on the printer, refer to:

https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer

And attach the result here.

Chris

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Yes, the printer still prints the error page with the lpadmin line.

Here's the output from the "Getting the data which would go to the printer".

Revision history for this message
Jeremy Bícha (jbicha) wrote :

And here's the output from Ubuntu 12.04 for comparison.

Revision history for this message
cliddell (cjl) wrote :

Jeremy,

If you don't mind, could you do me favour, and repeat the test print after doing:

lpadmin -p test -o psdebug=true

(assuming you called your file output queue "test" as suggested in "Getting the data which would go to the printer"), please?

It's just it will save time if I don't have to "manually" decompress the file content.

Thanks,

Chris

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

It must be

lpadmin -p test -o psdebug-default=true

and

lpadmin -p test -R psdebug-default

removes the setting.

Per-job it is

lpr -P test -o psdebug=true file

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cups-filters (Ubuntu) because there has been no activity for 60 days.]

Changed in cups-filters (Ubuntu):
status: Incomplete → Expired
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.