Release print job does nothing

Bug #1295064 reported by Phill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
system-config-printer (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I right-click on a print job that is in the "Held" status and choose "Release" nothing happens. I would expect it to start printing almost immediately. I get the same result using the toolbar "Play" button. The job eventually releases itself after 5 minutes.

The job goes into the "held" status usually because the printer isn't ready when I printed it (I rarely use my printer so it's normally turned off). However even after the printer is connected and shows as "Idle" in "Settings->Printers" and even prints new jobs while the old one is stuck in the "held" status, the release function does not work.

It seems that the only option is to wait 5 minutes, or cancel the job and re-print. I'm sure that the release function used to work in older versions as I've had this configuration for years.

I found the following steps reproduce the problem easily (turn networking on/off instead of the printer as it's a quicker and cleaner than waiting for printer to get its act together):

1) Set up a network printer
2) Make sure everything is working and you are able to print a page
3) Turn off networking
4) Attempt to print a page
5) View it's status in the queue showing "held" (from the status icon)
6) Turn on networking
7) Try to release the job from (from the queue from the status icon)
8) Observe nothing happens
9) Print a differnt page
10) Observe the new page prints immediately
11) Wait for the original page to print after 5 minutes

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: cups 1.7.0~rc1-0ubuntu5.2
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CupsErrorLog:

Date: Thu Mar 20 10:04:16 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-05-03 (320 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
Lpstat: device for HP-Officejet-6500-E709n: hp:/net/Officejet_6500_E709n?zc=dhcppc30
MachineType: System manufacturer V-P5G45
MarkForUpload: True
Papersize: a4
PpdFiles: HP-Officejet-6500-E709n: HP Officejet 6500 e709n, hpcups 3.13.9
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=1fb8697a-7ed6-41e1-9a44-8c3728862ad7 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to saucy on 2014-02-10 (37 days ago)
dmi.bios.date: 05/18/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0405
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: V-P5G45
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: V-P5G45
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Phill (phill.l) wrote :
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Please follow the instructions in the section "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems. Activate debug logging as described and then do all steps for reproducing the bug as you mentioned in the description. After that attach the resulting error_log. Do not compress the file.

Changed in cups (Ubuntu):
status: New → Incomplete
affects: cups (Ubuntu) → system-config-printer (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for system-config-printer (Ubuntu) because there has been no activity for 60 days.]

Changed in system-config-printer (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.