Printer stops working after first print job

Bug #1017029 reported by Sandra Grabhorn
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using an HP LaserJet 5 (through a USB-to-parallel adapter). After a recent update (currently using CUPS 1.5.3-0Ubuntu1), the printer stopped accepting jobs after the first job.

One print job will print successfully, then all other jobs sit in the print queue because the printer is apparently not talking to the computer anymore. Rebooting or unplugging/replugging the printer's USB connector resolves this state, but only for one print job.

This appears to be similar in symptoms to bug 936629, but that appears to have been solved several months ago.

Attempted the following to resolve the problem, without success:

1. Uninstalling and reinstalling the printer.
2. Using 'aa-complain cupsd' as suggested in the above-referenced bug.
3. Turning off and on the blacklisting of the usblp module.
4. Turning off and on forced uni-directional printing.
5. Running through the automatic troubleshooter.

Attaching the following files, per https://wiki.ubuntu.com/DebuggingPrintingProblems:

Output of commands suggested in the "printer detection" section
error_log file from printer driver
troubleshoot output from automatic troubleshooter
(Not attaching a scan of the error page, since the error is that nothing is printed)

Revision history for this message
Sandra Grabhorn (smoltish) wrote :
Revision history for this message
Sandra Grabhorn (smoltish) wrote :
Revision history for this message
Sandra Grabhorn (smoltish) wrote :
description: updated
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
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.