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
Ricoh and Savin pxlmono printers have custom shell scripting in FoomaticRIPCommandLine. These printers hang at Processing with 0% CPU. As I reported for Ricoh:
Bisecting with the ALA shows that 2018/08/05 prints to the MP 2352 and 08/06 hangs. Partial upgrading a few packages at a time listed with pacman -Qqu from 8/5 to 8/6 shows that the printing problem is an incompatibility with glibc 2.28. Unfortunately downgrading glibc is not an option because many system components require glibc>=2.28 including Chrome and Firefox.
I put the lines into a shell script and added, changed, and removed lines. Nothing would print. The only way I found to get these printers to print is to remove all the extra shell scripting and leave only the gs command similar to the one in the HP LaserJet 4100 Foomatic/pxlmono which prints without hang and as described here.
This states that cups changes behavior between a FoomaticRIPCommandLine that starts with "gs " and one that starts with anything else.
I have tried to modify the ppd and force the FoomaticRIPCommandLine to "gs -q -dBATCH -dPARANOIDSAFER -dNOPAUSE -dNOINTERPOLATE %B%A%C %D%E". In this case no pdftops conversion is performed, but I'm not sure what I am losing. Why are the extra printf/perl commands needed? Am I losing some printing options in this way? If this is true, couldn't this options be added in another way?
aitziber
In my case preventing the extra step stops the hanging.
Ricoh and Savin pxlmono printers have custom shell scripting in FoomaticRIPCommandLine. These printers hang at Processing with 0% CPU. As I reported for Ricoh:
Test printers:
Ricoh Aficio MP 2352 , pxlmono-Ricoh 20161206 (OpenPrinting LSB 3.2)
Savin 9060 , pxlmono-Savin 20161206 (OpenPrinting LSB 3.2)
I put the lines into a shell script and added, changed, and removed lines. Nothing would print. The only way I found to get these printers to print is to remove all the extra shell scripting and leave only the
gs
command similar to the one in theHP LaserJet 4100 Foomatic/pxlmono
which prints without hang and as described here.Printing [Foomatic] FoomaticRIPCommandLine for PDF as Standard Print Job Format?
This states that cups changes behavior between a FoomaticRIPCommandLine that starts with "gs " and one that starts with anything else.
In my case preventing the extra step stops the hanging.
HTop:
cupsctl --debug-logging, print, cancel job
job334.log.zip
The text was updated successfully, but these errors were encountered: