Hide Forgot
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.
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
Created attachment 560491 [details] debugging output of updates-testing cups version as requested
Does it work OK over AppSocket protocol ? socket://192.168.123.200:9100
Yes.
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
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
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.
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.
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.