cups-filters 1.13.4 failures

Dennis Glatting freebsd at pki2.com
Mon Mar 27 05:52:00 UTC 2017


On Mon, 2017-03-27 at 18:37 +1300, Jonathan Chen wrote:
> Hi,
> 
> I recently updated to cups-filters 1.13.4, and it appears that I now
> cannot print PDF files. The port is built with the default options.
> The logs indicate:
> 
> D [27/Mar/2017:17:24:32 +1300] [Job 631] Running command line for
> pdftops: pdftops -level3 /var/spool/cups/tmp/0410d58dfd707 -
> D [27/Mar/2017:17:24:32 +1300] [Job 631] Started filter pdftops (PID
> 16655)
> D [27/Mar/2017:17:24:32 +1300] [Job 631] Unable to execute pdftops
> program: No such file or directory
> D [27/Mar/2017:17:24:32 +1300] [Job 631] Started filter pstops (PID
> 16656)
> D [27/Mar/2017:17:24:32 +1300] [Job 631] PID 16655 (pdftops) stopped
> with status 1!
> D [27/Mar/2017:17:24:32 +1300] [Job 631] The print file is empty.
> D [27/Mar/2017:17:24:32 +1300] [Job 631] PID 16656 (pstops) stopped
> with status 1!
> D [27/Mar/2017:17:24:32 +1300] [Job 631] Sent 0 bytes...
> D [27/Mar/2017:17:24:32 +1300] [Job 631] Waiting for read thread to
> exit...
> D [27/Mar/2017:17:24:32 +1300] [Job 631] PID 16653
> (/usr/local/libexec/cups/filter/pdftops) stopped with status 1.
> 
> I am not sure why its complaining that pdftops is not there because
> both the filter and the main program are there:
> 6:27pm# ls -l /usr/local/libexec/cups/filter/pdftops
> -rwxr-xr-x  1 root  wheel  36672 25 Mar 15:05
> /usr/local/libexec/cups/filter/pdftops
> 6:32pm# ls -l /usr/local/bin/pdftops
> -rwxr-xr-x  1 root  wheel  18744  8 Jan 13:43 /usr/local/bin/pdftops*
> 
> Is the filter looking for pdftops in the wrong place?
> 
> 6:36pm# strings /usr/local/libexec/cups/filter/pdftops | grep
> bin.pdftops
> /usr/bin/pdftops
> 

I have the same problem and traced it to something between pdftopdf and
pdftops (pdftopdf exits with no errors). Pdftopdf creates a file in
/var/spool/cups/tmp but when pdftops is called the file doesn't exist.
No idea why. Changing permissions didn't help. Truss didn't help. To my
surprise, swearing didn't help either.





> Cheers.


More information about the freebsd-ports mailing list