Bug 788604

Summary: After every print job on ipp: Unable to get print job status
Product: [Fedora] Fedora Reporter: Mebus <mebus>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: jpopelka, mike, twaugh, wbachman
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 15:10:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
debugging output of updates-testing cups version none

Description Mebus 2012-02-08 15:17:57 UTC 
Description of problem:

After every print job, cups stops the printer and prints "Unable to get print job status" in the CUPS printer status message. It's a Oki C5900 connected via IPP. Driver is: "OKI C5900(PS)"

Manually re-enabling the printer prints the following job - and stops again!

Version-Release number of selected component (if applicable):

CUPS 1.5.0
cups-1.5.0-22.fc16.i686

How reproducible:

Connect printer, print one document, see printer beeing stopped.
Comment 1 Jiri Popelka 2012-02-09 09:26:04 UTC 
Please update cups with:
su -c 'yum update --enablerepo=updates-testing cups'
and then get an output from Printing troubleshooter
https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter
and attach it to this BZ.

thanks
Comment 2 Mebus 2012-02-09 10:14:31 UTC 
Created attachment 560491 [details]
debugging output of updates-testing cups version

as requested
Comment 3 Jiri Popelka 2012-02-09 10:48:50 UTC 
Does it work OK over AppSocket protocol ?
socket://192.168.123.200:9100
Comment 4 Mebus 2012-02-09 10:53:14 UTC 
Yes.
Comment 5 Jiri Popelka 2012-02-09 10:57:42 UTC 
Could you also experiment a little with IPP URI Options ?
http://www.cups.org/documentation.php/network.html#PROTOCOLS

Maybe something like:
ipp://192.168.123.200/ipp?waitjob=false&waitprinter=false
Comment 6 W. Michael Petullo 2012-06-13 18:21:16 UTC 
I have the same symptom on Fedora 17. Printer is a HP LaserJet 4250 using dnssd://hp%20LaserJet%[...]._ipp._tcp.local/.

cups-1.5.2-12.fc17.x86_64
Comment 7 Tim Waugh 2012-06-20 16:17:53 UTC 
Anyone seeing this: please try to use the "waitjob" and "waitprinter" options (see comment #5) in the ipp device URI for the printer and report the results.

W. Michael Petullo: you'll first need to change your device URI to an ipp: scheme.  If you run "cupsctl --debug-logging", then send a print job, then run "cupsctl --no-debug-logging", you should see a line in /var/log/cups/error_log like this:

DEBUG: Resolved as "..."...

That should be your ipp:-scheme device URI.  First, try using that URI instead of the dnssd one.  Next, try adding the waitjob/waitprinter options to the end.
Comment 8 Wes Bachman 2012-08-06 16:56:49 UTC 
I was seeing this issue with a C3765dnf.  I added the waitjob and waitprinter options as mentioned in comment #5, and I no longer seem to be seeing the problem.
Comment 9 Tim Waugh 2012-08-07 15:10:04 UTC 
Wes: thanks. It seems like this printer does not support IPP very well. A newer version of system-config-printer prefers other types of communication to IPP, so perhaps that would avoid the problem in future.