Cups waiting for job completed ошибка linux

This problem is described in detail in https://bugzilla.redhat.com/show_bug.cgi?id=1207154 and was fixed by changing gnome-settings-daemon, maybe we can reuse the fix?

Expected behaviour

cups-waiting-for-job-completed notification is displayed without the title «Printer error» or not displayed at all.

Actual behaviour

cups-waiting-for-job-completed notification is displayed with the title «Printer error». But documents print just fine.

Steps to reproduce the behaviour

When printing to a network printer use any of the ipp, lpd, socket, or dnssd backends, the cups-waiting-for-job-completed job state reason is normal and should not cause a desktop notification.

MATE general version

All in the range 1.18.x

Package version

mate-settings-daemon 1.18.2-1
cups 2.2.6

Linux Distribution

Manjaro Linux

Link to downstream report of your Distribution

None

I’m on Fedora 24 and am trying to print.

My printer is a Brother MFC-J6520DW which worked well on Debian. I installed the driver from Brother’s webpage.

Whenever I try to print a test page, the printer status never gets beyond «Processing — Waiting for job to complete». On the screen of the printer itself it says «Retrieving Data». After a very long time (some minutes) the printer releases an empty page.

The printer sits on a network and works fine from other non-Fedora devices.

I have tried the following:

• explicitly allow MyUser in the CUPS webinterface (locahost:631)
• ensured that the ipp and ipp-client services are trusted by the firewall (I understand that these are needed for printing).

Not really sure what to do next to try to fix this….

Even though this post was from 2016 I was having the same problem in 2019 with the printer error message «printer error. . .cups waiting for job complete.» I wanted to thank Hendrick for providing the above solution that was successful for me — he recommended adding «waiteof=false’ parameter in the printer configuration.

To accomplish this, I executed ‘netstat -r’ from the command line to get the IP address of my network printer. Then I went to ‘Printers’ in the Application Menu and right clicked on my network printer. Under Properties > Settings > Device URI, I replaced the existing text with the following:

socket://<ip address>:9100/?waiteof=false

where <ipaddress> is the IP address you determined by using ‘netstat -r’ as noted above and 9100 is the customary port number for networked printers. If your IP address were 192.168.1.8 the command would read as follows:

socket://192.168.1.8:9100/?waiteof=false

No more error messages thanks to Hendrick!

-Allen

CUPS has 3 fields that are used in issue reporting,

1. printer-state (enum): Either idle, processing or stopped.
2. printer-state-message: Plain text human readable explanation.
3. printer-state-reasons: Listed description of the printer state, as described in RFC8011 p.152 this is where the real issue reporting happens. It has a list of comma delimited keywords describing the state of a printer eg. ‘media-needed’ or ‘toner-low’

When testing a Zebra LP 2844 on Ubuntu 16.04 (and mac but let’s keep this simple for now) using the Zebra EPL2 Label Printer driver, I get the following results.

----Printer out of paper----
Status Enum: processing
Status Message: printer-state-message: 1 textWithoutLanguage {Waiting for 
printer to become available.}
Status Reason: printer-state-reasons: 1 keyword {none}

----Printer rejecting jobs----
Status Enum: idle
Status Message: printer-state-message: 1 textWithoutLanguage {Rejecting Jobs}
Status Reason: printer-state-reasons: 1 keyword {none}

As you can see, the ‘Printer out of paper’ issue and most issues that prevent the printer from printing resolve as ‘processing’ and never give me more information. You could figure out how long the printer has been ‘processing’ and deduce if there is a problem from there, but besides that being janky, the cause of the issue would remain unknown.

Meanwhile, the ‘Printer rejecting jobs’ state tells me absolutely nothing (remember, the Status Message is just human readable plain text and is not parsable due to there being no guidelines on what is put there). Besides hiring someone to read state-message there is no way for my program to know there is an issue.

This is not the case with all printers, for example, this is the output from a Brother HL-L2380DW

----Printer out of paper----
Status Enum: processing
Status Message: printer-state-message: 1 textWithoutLanguage {Waiting for job to complete.}
Status Reason: printer-state-reasons: 2 keyword {cups-waiting-for-job-completed, media-needed-error} 

Of the 3 printers tested so far (HP, Brother, and Zebra), the Brother HL-L2380DW was the only printer to properly communicate issues. If you wish to test it yourself you can run this crude CUPS tool I tossed together in java https://github.com/Vzor-/cupstool More data helps!

I do not know if the issue lies with cups or with the manufacturers. Either way I need a way forward, be it as a fix or a group I can help to make a fix.

Edit: It seems Zebra does not make or maintain its own Linux drivers.