-
Notifications
You must be signed in to change notification settings - Fork 469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipp backend doesn't wait as it should #761
Comments
CUPS.org User: mike We can't accept the patch as-is, since it does not conform to the CUPS CMP coding style requirements, and I'm not keen on using goto in any of our code if it can be avoided. Will look into this some more and see if I can come up with a simpler fix. |
CUPS.org User: mike I implemented a simpler fix which queries the printer at the end of all job processing. |
CUPS.org User: mike Fixed in CVS - the anonymous CVS repository will be updated at midnight EST. |
"debug.patch": --- cups-1.1.21rc1/backend/ipp.c.debug 2004-06-08 13:06:39.000000000 -0400
fputs("INFO: Waiting for job to complete...\n", stderr);
@@ -985,11 +991,14 @@
/*
/*
exit(1); |
Version: 1.1.21rc1
CUPS.org User: mclasen.redhat
I found that the ipp backend only waits for the job completion if waitjob is 1 and argc > 6. This may be intentional, but it has the consequence that printer status is not reported back to the daemon, because the code
block after
/*
* Now check on the printer state...
*/
is never reached. After changing that I discovered that the
"Waiting for job to complete" printer status_message never gets cleared, so I had to make the ipp backend emit an empty INFO message to clear it.
My patch does three things:
loop is always reached if waitjob is 1
in the loop.
The text was updated successfully, but these errors were encountered: