Bug#931363: Fails to create output PDF (permission denied)

2020-11-27 Thread Roland Hieber
I was stumbling over this today too… but a look at the code shows that
the log output is confusing.

On Wed, Jul 03, 2019 at 09:52:29AM +0200, martin f krafft wrote:
>  Wed Jul  3 09:40:55 2019  [DEBUG] output filename created: 
> /home/ssd/madduck/PDF/stdin___madduck_PDF.pdf

Here, the output filename is built from other variables,

>  Wed Jul  3 09:40:55 2019  [DEBUG] ghostscript commandline built: /usr/bin/gs 
> -q -dCompatibilityLevel=1.4 -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 
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702

then the gs commandline is built,

>  Wed Jul  3 09:40:55 2019  [DEBUG] output file unlinked: 
> /home/ssd/madduck/PDF/stdin___madduck_PDF.pdf

then the output file is unlinked so that gs does not have problems
writing to it,

>  Wed Jul  3 09:40:55 2019  [DEBUG] TMPDIR set for GhostScript: /var/tmp

and only here the gs process is forked off.

>  Wed Jul  3 09:40:55 2019  [DEBUG] waiting for child to exit
>  Wed Jul  3 09:40:55 2019  [DEBUG] entering child process
>  Wed Jul  3 09:40:55 2019  [DEBUG] GID set for current user
>  Wed Jul  3 09:40:55 2019  [DEBUG] supplementary groups set for current user
>  Wed Jul  3 09:40:55 2019  [DEBUG] UID set for current user: madduck
>  Wed Jul  3 09:40:55 2019  [DEBUG] ghostscript has finished: 256

However, gs exits unsucessfully with an exit code of 256.

>  Wed Jul  3 09:40:55 2019  [DEBUG] no postprocessing
>  Wed Jul  3 09:40:55 2019  [DEBUG] spoolfile unlinked: 
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>  Wed Jul  3 09:40:55 2019  [DEBUG] all memory has been freed
> 
> Not only is the output file unlinked right after the call to /usr/bin/gs;
> 
> The target directory is 0700, but even changing it to 1777 doesn't fix
> things.
> 
> Note that if I reduce the LogLevel to 3 in /etc/cups/cups-pdf.conf, then the
> log output suggests that PDF creation is being successful, after failing to
> set the file mode:
> 
>  Wed Jul  3 09:44:00 2019  [ERROR] failed to set file mode for PDF file: 
> /home/ssd/madduck/PDF/2019-07-03-094400-740472161-muttprint.pdf (non fatal)

This is only a follow-up error because gs did not create the output
file. So I would also look for the cause in gs itself, or the
environment in which it was executed.

But that's all I could find out until now…

 - Roland



Bug#931363: Fails to create output PDF (permission denied)

2019-09-25 Thread martin f krafft

Quoting "intrigeri", who wrote on 2019-09-18 at 08:42 Uhr +0200:

Martin, could you please confirm this fixes the problem for you?


Thanks for looking into this. Unfortunately, adding /home/ssd to 
HOMEDIRS and reloading apparmor didn't have the desired effect. I 
was also not aware of actually having apparmor enabled on this 
machine.


Anyway, the problem persists, unfortunately.

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

"the ships hung in the sky in much the same way that bricks don't."
-- hitchhiker's guide to the galaxy


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


Bug#931363: Fails to create output PDF (permission denied)

2019-09-18 Thread intrigeri
Control: tag -1 + moreinfo

Hi,

Brian Potkin:
> I wonder whether apparmor is involved? The journal is a place to look.

Indeed. It looks like Martin's $HOME directory is /home/ssd/madduck,
which is not covered by AppArmor's default @{HOME} tunable ("variable").

I suspect Martin will thus see AppArmor denials in his kernel logs.

To teach AppArmor about this local non-standard home directory layout,
add this line to /etc/apparmor.d/tunables/home.d/site.local :

  @{HOMEDIRS}+=/home/ssd/

Then reload the cups profile(s):

  sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.cupsd

Martin, could you please confirm this fixes the problem for you?

Thanks in advance!

Cheers,
-- 
intrigeri



Bug#931363: Fails to create output PDF (permission denied)

2019-07-06 Thread Brian Potkin
On Sat 06 Jul 2019 at 12:29:18 +0300, Martin-Éric Racine wrote:

> I made further tests on Stretch. My current packages:
> 
> $ dpkg -l | grep -e ghostscript -e cups-pdf | awk '{print $2, $3}'
> ghostscript 9.26a~dfsg-0+deb9u3
> printer-driver-cups-pdf 2.6.1-22
> 
> Test 1: print an UTF-8 text file from Gedit.  Works.
> 
> Test 2: print an ODF document from LibreOffice. Works.
> 
> Test 3: print an HTML document from Firefox-ESR. Works.
> 
> This bug thus seems to occur rather randomly.  For the record, I
> indeed encountered a "permission denied" error when I tried printing
> to PDF the other day, but I no longer remember from which application
> I did. I probably pressed CTRL-P in whichever application I was using
> at that moment.

>From everything that has been said, the filtering system appears to be
doing its job correctly. This can be confirmed (as root) with

cupsfilter -p  -m printer/foo -e  > out.pdf

I wonder whether apparmor is involved? The journal is a place to look.

Chheers,

Brian.



Bug#931363: Fails to create output PDF (permission denied)

2019-07-06 Thread Martin-Éric Racine
I made further tests on Stretch. My current packages:

$ dpkg -l | grep -e ghostscript -e cups-pdf | awk '{print $2, $3}'
ghostscript 9.26a~dfsg-0+deb9u3
printer-driver-cups-pdf 2.6.1-22

Test 1: print an UTF-8 text file from Gedit.  Works.

Test 2: print an ODF document from LibreOffice. Works.

Test 3: print an HTML document from Firefox-ESR. Works.

This bug thus seems to occur rather randomly.  For the record, I
indeed encountered a "permission denied" error when I tried printing
to PDF the other day, but I no longer remember from which application
I did. I probably pressed CTRL-P in whichever application I was using
at that moment.

Martin-Éric




ke 3. heinäk. 2019 klo 15.39 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ke 3. heinäk. 2019 klo 14.51 martin f krafft (madd...@debian.org) kirjoitti:
> >
> > I straced gs run directly (as user "nobody"), as well as gs run from
> > cupsd. After replacing all hex addresses with 0xdeadbeef, the two
> > traces are nigh identical, except cupsd seems to close FDs 0–2, so
> > that when run from cupsd, the first FD used is 0, whereas it's 3
> > otherwise.
> >
> > Apart from that, I see absolutely no difference in the syscalls
> > until one of the fails to write the output file.
> >
> > Straces attached. Go ahead load them in vimdiff!
>
> Thanks. Let's see if we can figure out what causes this.
>
> Volker: please see the whole thread at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931363
>
> Thanks!
> Martin-Éric



Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
ke 3. heinäk. 2019 klo 14.51 martin f krafft (madd...@debian.org) kirjoitti:
>
> I straced gs run directly (as user "nobody"), as well as gs run from
> cupsd. After replacing all hex addresses with 0xdeadbeef, the two
> traces are nigh identical, except cupsd seems to close FDs 0–2, so
> that when run from cupsd, the first FD used is 0, whereas it's 3
> otherwise.
>
> Apart from that, I see absolutely no difference in the syscalls
> until one of the fails to write the output file.
>
> Straces attached. Go ahead load them in vimdiff!

Thanks. Let's see if we can figure out what causes this.

Volker: please see the whole thread at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931363

Thanks!
Martin-Éric



Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread martin f krafft
I straced gs run directly (as user "nobody"), as well as gs run from 
cupsd. After replacing all hex addresses with 0xdeadbeef, the two 
traces are nigh identical, except cupsd seems to close FDs 0–2, so 
that when run from cupsd, the first FD used is 0, whereas it's 3 
otherwise.


Apart from that, I see absolutely no difference in the syscalls 
until one of the fails to write the output file.


Straces attached. Go ahead load them in vimdiff!

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

"it takes more keystrokes to enter a windows license key
than it takes to do a complete debian desktop install!"
   -- joey hess


gs-run-from-cupsd.strace.xz
Description: application/xz


gs-run-from-shell.strace.xz
Description: application/xz


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


Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread martin f krafft

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  @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


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


Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
ke 3. heinäk. 2019 klo 14.08 martin f krafft (madd...@debian.org) kirjoitti:
>
> Quoting "Martin-Éric Racine", who wrote on 2019-07-03 at 13:06 Uhr +0300:
> >My best guess is that you bumped into a symptom of upgrading from
> >cups-pdf 2 to cups-pdf 3.  The back-end has changed and maintainer
> >scripts make no attempt to upgrade the backend used by any existing
> >PDF queue. If you purge and re-install the package, does file creation
> >still fail?
>
> Yes. I purged and reinstalled, and the problem persists. I even
> removed the printer and reinstalled it. The same problem seems to be
> the case: the gs process is failing to write to the output
> directory, even if the directory is set to 777.

I just tried on my stable host.  This used to work until a few weeks
ago, but it no longer does. 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.

Martin-Éric



Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread martin f krafft

Quoting "Martin-Éric Racine", who wrote on 2019-07-03 at 13:06 Uhr +0300:
My best guess is that you bumped into a symptom of upgrading from 
cups-pdf 2 to cups-pdf 3.  The back-end has changed and maintainer 
scripts make no attempt to upgrade the backend used by any existing 
PDF queue. If you purge and re-install the package, does file creation 
still fail?


Yes. I purged and reinstalled, and the problem persists. I even 
removed the printer and reinstalled it. The same problem seems to be 
the case: the gs process is failing to write to the output 
directory, even if the directory is set to 777.


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

fitter, healthier, more productive
like a pig, in a cage, on antibiotics
   -- radiohead


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


Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
ke 3. heinäk. 2019 klo 12.40 martin f krafft (madd...@debian.org) kirjoitti:
>
> Quoting "Martin-Éric Racine", who wrote on 2019-07-03 at 11:18 Uhr +0300:
> >Is the host where this fails running a cups-pdf that was upgraded from 
> >previous
> >releases?
>
> Yes, just like the other host too. These are ancient systems,
> probably pre-sarge ;)

My best guess is that you bumped into a symptom of upgrading from
cups-pdf 2 to cups-pdf 3.  The back-end has changed and maintainer
scripts make no attempt to upgrade the backend used by any existing
PDF queue. If you purge and re-install the package, does file creation
still fail?

Martin-Éric



Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread martin f krafft

Quoting "Martin-Éric Racine", who wrote on 2019-07-03 at 11:18 Uhr +0300:
Is the host where this fails running a cups-pdf that was upgraded from previous 
releases? 


Yes, just like the other host too. These are ancient systems, 
probably pre-sarge ;)


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

if you find a spelling mistake in the above, you get to keep it.


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


Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
Hey Martin,

Thanks for this bug report.

Is the host where this fails running a cups-pdf that was upgraded from
previous releases?

Martin-Éric


ke 3. heinäk. 2019 klo 11.09 martin f krafft (madd...@debian.org) kirjoitti:

> Package: printer-driver-cups-pdf
> Version: 3.0.1-5
> Severity: normal
>
> The PDF driver is failing to write the output PDFs. For example, a
> command like
>
>   echo foo | lp -d PDF
>
> yields the following DEBUG output in the log:
>
>   Wed Jul  3 09:40:55 2019  [DEBUG] *** Final Configuration ***
>   Wed Jul  3 09:40:55 2019  [DEBUG] AnonDirName=
> "/var/spool/cups-pdf/ANONYMOUS"
>   Wed Jul  3 09:40:55 2019  [DEBUG] AnonUser   = "nobody"
>   Wed Jul  3 09:40:55 2019  [DEBUG] GhostScript= "/usr/bin/gs"
>   Wed Jul  3 09:40:55 2019  [DEBUG] GSCall = "%s -q
> -dCompatibilityLevel=%s -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite
> -sOutputFile="%s" -dAutoRotatePages=/PageByPage
> -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode
> -dPDFSETTINGS=/prepress -c .setpdfwrite -f %s"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Grp= "lpadmin"
>   Wed Jul  3 09:40:55 2019  [DEBUG] GSTmp  = "TMPDIR=/var/tmp"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Log= "/var/log/cups"
>   Wed Jul  3 09:40:55 2019  [DEBUG] PDFVer = "1.4"
>   Wed Jul  3 09:40:55 2019  [DEBUG] PostProcessing = ""
>   Wed Jul  3 09:40:55 2019  [DEBUG] Out= "${HOME}/PDF"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Spool  =
> "/var/spool/cups-pdf/SPOOL"
>   Wed Jul  3 09:40:55 2019  [DEBUG] UserPrefix = ""
>   Wed Jul  3 09:40:55 2019  [DEBUG] RemovePrefix   = ""
>   Wed Jul  3 09:40:55 2019  [DEBUG] OutExtension   = "pdf"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Cut= -1
>   Wed Jul  3 09:40:55 2019  [DEBUG] Truncate   = 256
>   Wed Jul  3 09:40:55 2019  [DEBUG] DirPrefix  = 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] Label  = 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] LogType= 4
>   Wed Jul  3 09:40:55 2019  [DEBUG] LowerCase  = 1
>   Wed Jul  3 09:40:55 2019  [DEBUG] TitlePref  = 1
>   Wed Jul  3 09:40:55 2019  [DEBUG] DecodeHexStrings   = 1
>   Wed Jul  3 09:40:55 2019  [DEBUG] FixNewlines= 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] AllowUnsafeOptions = 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] AnonUMask  = 
>   Wed Jul  3 09:40:55 2019  [DEBUG] UserUMask  = 0077
>   Wed Jul  3 09:40:55 2019  [DEBUG] *** End of Configuration ***
>   Wed Jul  3 09:40:55 2019  [DEBUG] set new gid: lpadmin
>   Wed Jul  3 09:40:55 2019  [DEBUG] initialization finished: v3.0.1
>   Wed Jul  3 09:40:55 2019  [DEBUG] user identified: madduck
>   Wed Jul  3 09:40:55 2019  [DEBUG] output directory name generated:
> /home/ssd/madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] user information prepared
>   Wed Jul  3 09:40:55 2019  [DEBUG] spoolfile name created:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] source stream ready
>   Wed Jul  3 09:40:55 2019  [DEBUG] destination stream ready:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] owner set for spoolfile:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] using traditional fgets
>   Wed Jul  3 09:40:55 2019  [DEBUG] found beginning of postscript code:
> %!PS-Adobe-3.0
>
>   Wed Jul  3 09:40:55 2019  [DEBUG] now extracting postscript code
>   Wed Jul  3 09:40:55 2019  [DEBUG] found title in ps code: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] found end of postscript code: %%EOF
>
>   Wed Jul  3 09:40:55 2019  [DEBUG] all data written to spoolfile:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] trying to use commandline title:
>   Wed Jul  3 09:40:55 2019  [DEBUG] checking for hex strings:
>   Wed Jul  3 09:40:55 2019  [DEBUG] not a hex string, has no start marker:
>   Wed Jul  3 09:40:55 2019  [DEBUG] calling alternate_replace_string
>   Wed Jul  3 09:40:55 2019  [DEBUG] removing alternate special characters
> from title:
>   Wed Jul  3 09:40:55 2019  [DEBUG] empty commandline title, using PS
> title: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] checking for hex strings: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] not a hex string, has no start marker:
> ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] calling alternate_replace_string
>   Wed Jul  3 09:40:55 2019  [DEBUG] removing alternate special characters
> from title: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] removing leading _ from title:
> __stdin___madduck_PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] title successfully retrieved:
> stdin___madduck_PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] input data read from stdin
>   Wed Jul  3 09:40:55 2019  [DEBUG] output filename created:
> 

Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread martin f krafft

Package: printer-driver-cups-pdf
Version: 3.0.1-5
Severity: normal

The PDF driver is failing to write the output PDFs. For example, a 
command like


 echo foo | lp -d PDF

yields the following DEBUG output in the log:

 Wed Jul  3 09:40:55 2019  [DEBUG] *** Final Configuration ***
 Wed Jul  3 09:40:55 2019  [DEBUG] AnonDirName= 
"/var/spool/cups-pdf/ANONYMOUS"
 Wed Jul  3 09:40:55 2019  [DEBUG] AnonUser   = "nobody"
 Wed Jul  3 09:40:55 2019  [DEBUG] GhostScript= "/usr/bin/gs"
 Wed Jul  3 09:40:55 2019  [DEBUG] GSCall = "%s -q -dCompatibilityLevel=%s 
-dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile="%s" 
-dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode 
-dPDFSETTINGS=/prepress -c .setpdfwrite -f %s"
 Wed Jul  3 09:40:55 2019  [DEBUG] Grp= "lpadmin"
 Wed Jul  3 09:40:55 2019  [DEBUG] GSTmp  = "TMPDIR=/var/tmp"
 Wed Jul  3 09:40:55 2019  [DEBUG] Log= "/var/log/cups"
 Wed Jul  3 09:40:55 2019  [DEBUG] PDFVer = "1.4"
 Wed Jul  3 09:40:55 2019  [DEBUG] PostProcessing = ""
 Wed Jul  3 09:40:55 2019  [DEBUG] Out= "${HOME}/PDF"
 Wed Jul  3 09:40:55 2019  [DEBUG] Spool  = 
"/var/spool/cups-pdf/SPOOL"
 Wed Jul  3 09:40:55 2019  [DEBUG] UserPrefix = ""
 Wed Jul  3 09:40:55 2019  [DEBUG] RemovePrefix   = ""
 Wed Jul  3 09:40:55 2019  [DEBUG] OutExtension   = "pdf"
 Wed Jul  3 09:40:55 2019  [DEBUG] Cut= -1
 Wed Jul  3 09:40:55 2019  [DEBUG] Truncate   = 256
 Wed Jul  3 09:40:55 2019  [DEBUG] DirPrefix  = 0
 Wed Jul  3 09:40:55 2019  [DEBUG] Label  = 0
 Wed Jul  3 09:40:55 2019  [DEBUG] LogType= 4
 Wed Jul  3 09:40:55 2019  [DEBUG] LowerCase  = 1
 Wed Jul  3 09:40:55 2019  [DEBUG] TitlePref  = 1
 Wed Jul  3 09:40:55 2019  [DEBUG] DecodeHexStrings   = 1
 Wed Jul  3 09:40:55 2019  [DEBUG] FixNewlines= 0
 Wed Jul  3 09:40:55 2019  [DEBUG] AllowUnsafeOptions = 0
 Wed Jul  3 09:40:55 2019  [DEBUG] AnonUMask  = 
 Wed Jul  3 09:40:55 2019  [DEBUG] UserUMask  = 0077
 Wed Jul  3 09:40:55 2019  [DEBUG] *** End of Configuration ***
 Wed Jul  3 09:40:55 2019  [DEBUG] set new gid: lpadmin
 Wed Jul  3 09:40:55 2019  [DEBUG] initialization finished: v3.0.1
 Wed Jul  3 09:40:55 2019  [DEBUG] user identified: madduck
 Wed Jul  3 09:40:55 2019  [DEBUG] output directory name generated: 
/home/ssd/madduck/PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] user information prepared
 Wed Jul  3 09:40:55 2019  [DEBUG] spoolfile name created: 
/var/spool/cups-pdf/SPOOL/cups2pdf-8702
 Wed Jul  3 09:40:55 2019  [DEBUG] source stream ready
 Wed Jul  3 09:40:55 2019  [DEBUG] destination stream ready: 
/var/spool/cups-pdf/SPOOL/cups2pdf-8702
 Wed Jul  3 09:40:55 2019  [DEBUG] owner set for spoolfile: 
/var/spool/cups-pdf/SPOOL/cups2pdf-8702
 Wed Jul  3 09:40:55 2019  [DEBUG] using traditional fgets
 Wed Jul  3 09:40:55 2019  [DEBUG] found beginning of postscript code: 
%!PS-Adobe-3.0

 Wed Jul  3 09:40:55 2019  [DEBUG] now extracting postscript code
 Wed Jul  3 09:40:55 2019  [DEBUG] found title in ps code: ((stdin))
 madduck/PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] found end of postscript code: %%EOF

 Wed Jul  3 09:40:55 2019  [DEBUG] all data written to spoolfile: 
/var/spool/cups-pdf/SPOOL/cups2pdf-8702
 Wed Jul  3 09:40:55 2019  [DEBUG] trying to use commandline title:
 Wed Jul  3 09:40:55 2019  [DEBUG] checking for hex strings:
 Wed Jul  3 09:40:55 2019  [DEBUG] not a hex string, has no start marker:
 Wed Jul  3 09:40:55 2019  [DEBUG] calling alternate_replace_string
 Wed Jul  3 09:40:55 2019  [DEBUG] removing alternate special characters from 
title:
 Wed Jul  3 09:40:55 2019  [DEBUG] empty commandline title, using PS title: 
((stdin))
 madduck/PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] checking for hex strings: ((stdin))
 madduck/PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] not a hex string, has no start marker: 
((stdin))
 madduck/PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] calling alternate_replace_string
 Wed Jul  3 09:40:55 2019  [DEBUG] removing alternate special characters from 
title: ((stdin))
 madduck/PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] removing leading _ from title: 
__stdin___madduck_PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] title successfully retrieved: 
stdin___madduck_PDF
 Wed Jul  3 09:40:55 2019  [DEBUG] input data read from stdin
 Wed Jul  3 09:40:55 2019  [DEBUG] output filename created: 
/home/ssd/madduck/PDF/stdin___madduck_PDF.pdf
 Wed Jul  3 09:40:55 2019  [DEBUG] ghostscript commandline built: /usr/bin/gs -q 
-dCompatibilityLevel=1.4 -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 
/var/spool/cups-pdf/SPOOL/cups2pdf-8702
 Wed Jul  3 09:40:55 2019  [DEBUG] output