You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ipp backend seems to be the only one which tries to report printer state back to the scheduler. It does so by writing lines like
STATE: toner-low-warning,developer-empty-error
to stderr. The scheduler picks that up and feeds the string to SetPrinterStateReasons(). That function seems to accept three kinds of
input:
+reason1,reason2,... for adding reasons to the set of current reasons
-reason1,reason2,... for removing reasons from the set of current reasons
reason1,reason2,... for replacing the set of current reasons
the first two seem to work fine, but the third one (which is what the
ipp backend uses) doesn't. To fix it, you have to remove the
s[0] == '+' condition from the if in printers.c:1745. Patch attached.
The text was updated successfully, but these errors were encountered:
Version: 1.1.21rc1
CUPS.org User: mclasen.redhat
The ipp backend seems to be the only one which tries to report printer state back to the scheduler. It does so by writing lines like
STATE: toner-low-warning,developer-empty-error
to stderr. The scheduler picks that up and feeds the string to SetPrinterStateReasons(). That function seems to accept three kinds of
input:
+reason1,reason2,... for adding reasons to the set of current reasons
-reason1,reason2,... for removing reasons from the set of current reasons
reason1,reason2,... for replacing the set of current reasons
the first two seem to work fine, but the third one (which is what the
ipp backend uses) doesn't. To fix it, you have to remove the
s[0] == '+' condition from the if in printers.c:1745. Patch attached.
The text was updated successfully, but these errors were encountered: