In both of these cases, the LP service created the F<id>-<num> files
because it determined that it needed to convert the application provided
input to PostScript in order to print. This is likely to have happened
because the application tagged the job data as something other than
PostScript even though it sent PostScript data. What do the <id>-0 and
<id>-attributes files contain?
-Norm
Giovanni Schmid wrote:
> Hi Ghee,
>
> following your instructions I discovered that, in response to a print
> launched in gedit and scheduled as job <printer_name>-<id>, two files named
> <id>-<num> and F<id>-<num> are created in /var/spool/lp/temp, and both are
> recognized as postscript files by the system.
> E.g, job hp2300-20 results in the two files named 20-1 and F20-1, and both
> appear to be postscript files. Nevertheless, <id>-<num> is rendered as
> postscript (by Evince), whereas F<id>-<num> results is the ASCII file of
> the postscript code.
>
> Instead, when a print job for a PDF/PS file is launched in Evince, the system
> creates just one file, named <id>-<num>, which is correctly printed.
> I suspect that, in the first case, the system sends to the printer the
> (wrong) file F<id>-<num>, instead of the correct one named <id>-<num>
