Since a ports update late May of a FreeBSD 12-STABLE r359866, cups-pdf
crashes. Furter, despite configured logging in cups-pdf.conf, there is
nothing logged at all in /var/log/cups/.
Cups itself still logs to error_log, but even in debug mode there is not
much to tell.
Having rebuilt all the
> On 15. Jun 2020, at 09:45, Per olof Ljungmark wrote:
>
What happens if you run the gs command on the pdf you’re printing directly:
> gs -q -dNOPAUSE -dBATCH -dSAFER -dNOMEDIAATTRS -sstdout=? -sDEVICE=ps2write
> -dShowAcroForm -sOUTPUTFILE=? -dLanguageLevel=2 -r300 -dCompressFonts=false
>
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
On 2020-06-15 09:50, Michael Gmelin wrote:
On 15. Jun 2020, at 09:45, Per olof Ljungmark wrote:
What happens if you run the gs command on the pdf you’re printing directly:
gs -q -dNOPAUSE -dBATCH -dSAFER -dNOMEDIAATTRS -sstdout=? -sDEVICE=ps2write
-dShowAcroForm -sOUTPUTFILE=? -dLangua
On Mon, 15 Jun 2020 12:03:17 +0200
Per olof Ljungmark wrote:
> On 2020-06-15 09:50, Michael Gmelin wrote:
> >
> >
> >> On 15. Jun 2020, at 09:45, Per olof Ljungmark
> >> wrote:
> >
> > What happens if you run the gs command on the pdf you’re printing
> > directly:
> >
> >
> >> gs -q
On 2020-06-14 09:10, George Mitchell wrote:
> I do package builds on one machine on my (small) network, using
> portmaster, and then distributes the built packages to my other
> machines. Last week, I decided to make python38, rather than
> python37, my default version on Python 3. Specifically,
