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
Version: 1.2-current CUPS.org User: jlovell
No event is generated when printer-state-message is changed, therefore clients don't notice these new messages.
Attached one-line patch fixes it by generating a CUPSD_EVENT_PRINTER_STATE_CHANGED -- this seems to be the closest event type...
Comments?
Thanks!
The text was updated successfully, but these errors were encountered:
CUPS.org User: mike
Fixed in Subversion repository.
Sorry, something went wrong.
"printer-state-message.patch":
--- scheduler/job.c (revision 6044) +++ scheduler/job.c (working copy) @@ -1764,6 +1764,7 @@ strlcpy(job->printer->state_message, message, sizeof(job->printer->state_message)); cupsdAddPrinterHistory(job->printer);
event |= CUPSD_EVENT_PRINTER_STATE_CHANGED;
}
if (!strchr(job->status_buffer->buffer, '\n'))
No branches or pull requests
Version: 1.2-current
CUPS.org User: jlovell
No event is generated when printer-state-message is changed, therefore clients don't notice these new messages.
Attached one-line patch fixes it by generating a CUPSD_EVENT_PRINTER_STATE_CHANGED -- this seems to be the closest event type...
Comments?
Thanks!
The text was updated successfully, but these errors were encountered: