Markus Feilner wrote:

Hallo, hat noch jemand Probleme mit dem Drucken von PDFs? Ich finde mehr und mehr PDFs von Webseiten, die nicht sauber unter Cups drucken lassen. Fehlermeldunge beziehen sich beispielsweise auf fehlende Color Profiles, Cups client zählt die Seiten hoch, kommt aber nie zum Abschluss, das PDF hängt in der Queue und blockiert auch folgende Druckaufträge.

Ich suche noch, any help welcome...

I recently had to upgrade my ancient printserver, I kept getting some odd error with a kyocera filter. -- Per Jessen, Zürich (26.4°C)

On 6/25/22 11:12, Carlos E. R. wrote:

How exactly are you using CUPS to print PDFs? I use an application (several) which would then send to CUPS.

{Wie genau verwenden Sie CUPS zum Drucken von PDFs? Ich verwende eine Anwendung (mehrere), die dann an CUPS gesendet wird.}

probably cups-pdf and imagemagick/ghostscript nanny permissions are likely the problem. If I recall correctly you need to edit (as root) /etc/ImageMagick-7-SUSE/policy.xml and comment and replace: <!-- <policy domain="module" rights="none" pattern="{PS,PDF,XPS}" /> --> <policy domain="module" rights="read|write" pattern="{PS,PDF,XPS}" /> For background, and the bug in ghostscript <= 9.23, see: ImageMagick security policy 'PDF' blocking conversion https://stackoverflow.com/q/52998331/3422102 -- David C. Rankin, J.D.,P.E.

David C. Rankin wrote:

probably cups-pdf and imagemagick/ghostscript nanny permissions are likely the problem.

If I recall correctly you need to edit (as root) /etc/ImageMagick-7-SUSE/policy.xml and comment and replace:

<!-- <policy domain="module" rights="none" pattern="{PS,PDF,XPS}" /> --> <policy domain="module" rights="read|write" pattern="{PS,PDF,XPS}" />

I was curious, we regularly print PDFs and I don't recall ever having had to fiddle with anything like that (for printing). Looking at my 15.2 system, it already has: <policy domain="coder" rights="write" pattern="PS" /> <policy domain="coder" rights="write" pattern="PS2" /> <policy domain="coder" rights="write" pattern="PS3" /> <policy domain="coder" rights="write" pattern="PDF" /> <policy domain="coder" rights="write" pattern="XPS" /> <policy domain="coder" rights="write" pattern="PCL" />

For background, and the bug in ghostscript <= 9.23, see:

The OP didn't mention what he is running on, but in 15.2, ghostscript is 9.52. -- Per Jessen, Zürich (21.9°C)

Nope that ImageMagick stuff didnt help, sorry... I really had to remove the printer on all of my machines, empty the /etc/cups directory, start from scratch (with Cups Webinterface (not with YAST!) on localhost:631) and then it worked. The config I created works on all machines. It seems 5 Tumbleweed machines suddenly lost ipp:// connectivity. Strange. Detailed procedure: 0) After removing cups directory /etc/cups content, I created the printer with localhost:631 webinterface 1) Then I packed the /etc/cups directory (the new files) to a tarball and put them on all of my machines, where the printer now works fine again. I did not forget to follow these steps there: 1) service cups stop 2) mv /etc/cups /etc/cups.old 3) extract in etc/: tar xzf cups.gz 4) service cups start 5) lpq shows the printer. When comparing old and new config (printers.conf), the only difference I see is that now the URL ("DeviceURI") is socket://IP_of_printer where before it was ipp://... I wont go into research what happened, maybe someone else feels like doing that. I know enough about that that I worry what happened to IPP... on ALL my Tumbleweed systems (five in my local office) that all of them suddenly wouldn't print? This change must have happened 1-2 weeks ago. I was traveling, my office buddy had experienced the same. Thanks to all you guys out there, you do great work! Am Montag, 27. Juni 2022, 18:30:08 CEST schrieb Markus Feilner:

Thanks a lot! I always mix up English and German, I am sorry for that.

Yes, I remember that fix. I will look into it - but I am printing directly to a networked printer (HP Laserjet)

Am Montag, 27. Juni 2022, 11:13:13 CEST schrieb Per Jessen:

...

David C. Rankin wrote:

...

probably cups-pdf and imagemagick/ghostscript nanny permissions are likely the problem.

If I recall correctly you need to edit (as root)

/etc/ImageMagick-7-SUSE/policy.xml and comment and replace: <!-- <policy domain="module" rights="none" pattern="{PS,PDF,XPS}" /> -->

<policy domain="module" rights="read|write" pattern="{PS,PDF,XPS}" />

I was curious, we regularly print PDFs and I don't recall ever having had to fiddle with anything like that (for printing).

Looking at my 15.2 system, it already has: <policy domain="coder" rights="write" pattern="PS" /> <policy domain="coder" rights="write" pattern="PS2" /> <policy domain="coder" rights="write" pattern="PS3" /> <policy domain="coder" rights="write" pattern="PDF" /> <policy domain="coder" rights="write" pattern="XPS" /> <policy domain="coder" rights="write" pattern="PCL" />

...

For background, and the bug in ghostscript <= 9.23, see: The OP didn't mention what he is running on, but in 15.2, ghostscript is 9.52.

-- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - https://nitter.net/mfeilner ------------------------- Digital sovereignty in three words: "Exit Strategy First!" Digitale Souveränität in Drei Worten. ------------------------- Digitale Souveränität, Nachhaltigkeit, Dokumentation Linux, Security, Strategy, Politics, Journalism, Networking. https://www.feilner-it.net, 93059 Regensburg Wöhrdstr. 10, +49 170 302 7092 (+Signal) PGP: 40A3C306F96133067C11CFD9A958A906268C9F0A http://www.feilner-it.net/files/MFpub.asc Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner @mfeilner: Matrix, Jabber, Skype, Twitter, Diaspora, ...