Quoting "Martin-Éric Racine", who wrote on 2019-07-03 at 14:13 Uhr +0300:
I just tried on my stable host. This used to work until a few weeks ago, but it no longer does.

Can you reproduce the problem?

CUPS-PDF has not been updated, but Ghostscript has received security updates twice in recent times. I'm thus extremely tempted to reassign to Ghostscript.

I cannot reproduce the problem with Ghostscript. I used

 cd /var/spool/cups-pdf/SPOOL
 while :; do sudo ln * saved && break; done

to capture the temporary file, and then ran:

 /usr/bin/gs -q -dCompatibilityLevel=1.5 -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite 
-sOutputFile="/home/ssd/madduck/PDF/stdin___madduck_PDF.pdf" 
-dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false 
-dColorImageFilter=/FlateEncode -dPDFSETTINGS=/prepress -c .setpdfwrite -f /tmp/saved

as gleaned from the log. This created the PDF file just fine though.

If I use "sudo -u nobody" to run the process, then gs obviously fails, *unless* I make the target directory 1777, in which case it works and writes the PDF file.

However, gs, as called by cups-pdf, still fails to write the file in exactly the same setting.

What else could be different?

--
.''`.   martin f. krafft <madduck@d.o> @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
 `-  Debian - when you have better things to do than fixing systems

"if java had true garbage collection,
most programs would delete themselves upon execution."
                                                   -- robert sewell

Attachment: digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Reply via email to