Skip to content
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

Print jobs hang with custom FoomaticRIPCommandLine and glibc 2.28 #5396

Closed
severach opened this issue Sep 8, 2018 · 1 comment
Closed

Print jobs hang with custom FoomaticRIPCommandLine and glibc 2.28 #5396

severach opened this issue Sep 8, 2018 · 1 comment
Assignees
Labels
third-party This issue is in a third-party component

Comments

@severach
Copy link

severach commented Sep 8, 2018

*FoomaticRIPCommandLine: "(printf '\033%%-12345X@PJL\n@PJL JOB\n@PJL SET COPIES=&copies;\n'%G|perl -p -e "s/\x26copies\x3b/1/");
(gs -q -dBATCH -dPARANOIDSAFER -dNOPAUSE -dNOMEDIAATTRS -dNOINTERPOLATE %B%A%C %D%E | perl -p -e "s/^\x1b\x25-12345X//" | perl -p -e "s/\xc1\x01\x00\xf8\x31\x44/\x44/g");
(printf '@PJL\n@PJL EOJ\n\033%%-12345X')"
*End

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.

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 the HP 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.

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.

HTop:

11721 root       20   0 82264 14064  7280 S  0.0  0.0  0:00.46 ├─ /usr/bin/cupsd -l
16116 cups       20   0 82676 15880  6964 S  0.0  0.0  0:00.01 │  ├─ TestSavin 333 root Test Page 1 job-uuid=urn:uuid:9450815b-db4d-30bd-6873-b9c495e33601 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1536369858 time-at-processing=1536369858
16117 cups       20   0 58256  6232  4880 S  0.0  0.0  0:00.01 │  │  └─ pdftops 333 root Test Page 1  job-uuid=urn:uuid:9450815b-db4d-30bd-6873-b9c495e33601 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1536369858 time-at-processing=1536369858 /var/spool/cups/tmp/foomatic-YpTCST
16119 cups       20   0 59448  7080  5748 S  0.0  0.0  0:00.00 │  │     ├─ pdftops 333 root Test Page 1  job-uuid=urn:uuid:9450815b-db4d-30bd-6873-b9c495e33601 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1536369858 time-at-processing=1536369858
16118 cups       20   0  196M 27632 13092 S  0.0  0.1  0:01.74 │  │     └─ gs -q -dNOPAUSE -dBATCH -dSAFER -dNOMEDIAATTRS -sDEVICE=ps2write -dShowAcroForm -sOUTPUTFILE=%stdout -dLanguageLevel=3 -r600 -dCompressFonts=false -dNoT3CCITT -dNOINTERPOLATE -c save pop -f /var/spool/cups/tmp/foomatic-YpTCST

cupsctl --debug-logging, print, cancel job
job334.log.zip

@michaelrsweet
Copy link
Collaborator

Please file this bug against the cups-filters project. We have nothing to do with foomatic in this project...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
third-party This issue is in a third-party component
Projects
None yet
Development

No branches or pull requests

2 participants