Ricoh-Pro-1107EX authentication with PostScript driver broken

Bug #1004725 reported by rmcd
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
foomatic-db (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The Ricoh-Pro-1107EX printer driver has a PS and a PXL version. Using 12.,04, both fail but with different problems.

UPDATE: The PXL problem is already solved. It is bug 1002699.

The PS driver cannot print. If the printer's usercode feature is activated, printing fails with an "Access restricted" message. If the usercode feature is not activated, printing fails with a "Storing Failed" error.

The PXL driver prints, but it cannot print duplex or with finishing. When those are selected, the output is single-sided with no stapling.

This behavior is a regression. I have confirmed that printing works correctly with this printer using 10.04.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cups 1.5.2-9ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri May 25 16:26:54 2012
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327.1)
Lpstat:
 device for Lexmark-X364dn: usb://Lexmark/X364dn?serial=3501WPD&interface=1
 device for Ricoh-Pro-1107EX: lpd://129.105.195.10/PASSTHRU
MachineType: MSI MS-7585
Papersize: letter
PpdFiles:
 Ricoh-Pro-1107EX: Ricoh Pro 1107EX PXL
 Lexmark-X364dn: Lexmark X364dn
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=49f9878e-01cc-48cf-8700-bc63ead5d941 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/31/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.5
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P55-GD85 (MS-7585)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.5:bd12/31/2010:svnMSI:pnMS-7585:pvr1.0:rvnMSI:rnP55-GD85(MS-7585):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7585
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Revision history for this message
rmcd (rmcd1024) wrote :
affects: ubuntu → cups (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cups (Ubuntu):
status: New → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Probably it is due to foomatic-filters not passing options, bug 1002699.

Revision history for this message
rmcd (rmcd1024) wrote :

I can confirm that the fix in https://bugs.launchpad.net/bugs/1002699 (new foomatic-filter) fixes the problem with the PXL printer driver.

It does not fix the problem with the PS driver and authentication.

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

Thank you for testing.

With the fixed foomatic-filters installed and with the PostScript PPD in use, follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems, for a job which usercode.

summary: - Ricoh-Pro-1107EX printer driver broken
+ Ricoh-Pro-1107EX authentication with PostScript driver broken
Changed in cups (Ubuntu):
status: Confirmed → Incomplete
description: updated
Revision history for this message
rmcd (rmcd1024) wrote :

I did the following.

First, I verified that the usercode was operational using the plx printer driver. I put in a random usercode and received an "access restricted" message on the printer's job history screen. Using the correct usercode, the job printed.

Second, I attempted to print a small document using the Postscript printer driver. I first disabled the printer following the directions in reporting CUPS bugs. The printout file is attached. Next I re-enabled the printer and attempted to print. In all cases I receive an "access restricted" message when using the postscript driver.

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

I nedd also your error_log in debug mode, as described in comment #5.

Revision history for this message
rmcd (rmcd1024) wrote :

Sorry Till, I was focusing on holding all else fixed but authentication and I overlooked this.

It's attached. The "printout" file is identical to the one I already posted (I diffed to be sure). There were two print attempts with the printer disabled (it's possible the error code wasn't correct on the first) and the third after re-enabling the printer. All show "access restricted" on the printer's web print job history screen.

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

The problem is most probably in the PPD file supplied by Ricoh. I have informed the developers at Ricoh about this.

affects: cups (Ubuntu) → foomatic-db (Ubuntu)
Changed in foomatic-db (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in foomatic-db (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.