Description of problem: The latest (as of August 27 2012) version of cups - 1.5.4-1.fc17 cannot print via a cups server running on RHEL 6.3 cups-1.4.2.48. Downgrade of client needed. Version-Release number of selected component (if applicable): cups-1.5.4-1, cups-1.5.2-12 How reproducible: yum update f17 x86_64 which updates cups to 1.5.4-1. Then print via server running RHEL6.3 cups-1.4.2-48. The print job from the client is sent to the server but the server does not push it out to the printer. Once the client's cups is downgraded, the print works. Steps to Reproduce: 1. yum update fedora 17 client to update cups to cups-1.5.4-1 2. have a server running RHEL 6.3 cups-1.4.2-48. 3. send the print job via the RHEL print server and printing does not happen. Actual results: The printing should have completed but something is holding it back on the server. Additional Info: Setting up the actual printer directly in the cups definition of the client works with the new version of the cups but going via the server is not functional.
Could you attach an output from printing troubleshooter ? https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter We've already seen something similar in bug #827402. It turned out to be a problem in cups server configuration.
Jiri - Thanks for this. I will test it and report back. Harish
Created attachment 609525 [details] troubleshoot.txt with the printer in question on fc17 Here's the troubleshoot.txt file generated by the troubleshooter in system-config-printer in FC17.
'D [04/Sep/2012:10:44:13 +0800] [Job 2] Send-Document: cups-upgrade-required (Upgrade Required)', 'E [04/Sep/2012:10:44:13 +0800] [Job 2] Unable to add document to print job.', 'I [04/Sep/2012:10:44:13 +0800] [Job 2] Waiting for job to complete.', 'D [04/Sep/2012:10:44:13 +0800] [Job 2] update_reasons(attr=0(), s="+cups-remote-pending-held")', Closing as duplicate of bug #827402. I already told (via e-mail) Harish to contact servicedesk to fix the configuration of the cups server. *** This bug has been marked as a duplicate of bug 827402 ***