Bug#928738: closed by Brian Potkin <claremont102@gmail.com> (Re: Bug#928738: printer-driver-cups-pdf Still Produces PDF Files that Lack Searchable Text and are Unusable with pdftotext)

[Neil Ormos <ormos-deb1110@ormos.org>]

Debian Bug Tracking System wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the printer-driver-cups-pdf package:

> #928738: printer-driver-cups-pdf Still Produces PDF Files that Lack Searchable Text and are Unusable with pdftotext

> It has been closed by Brian Potkin <claremont102@gmail.com>. [...]

> [...] Sorry, Neil, but you are not using a
> 3.0.1-5 version of cups-pdf. I have no option
> but to close this report.

Hi Brian:

1.  Thanks for the hint.  I removed and reinstalled the package.  Lo and behold,

        pdftops-renderer=pdftocairo

    now appears in the report from lpoptions, "cairo" appears in the creator field reported by pdfinfo, and the PDF file contains searchable text.

2.  BEFORE removing and reinstalling, I checked dpkg -l, which reported:

        ii  printer-driver-cups-pdf  3.0.1-5     amd64       printer driver for PDF writing via CUPS

    And I also checked /var/log/dpkg.log, which included this line from yesterday:

        2019-05-09 16:26:18 status installed printer-driver-cups-pdf:amd64 3.0.1-5

    I saw nothing in the log that suggested that the original installation failed.

    I have no idea why the new print queue including the pdftops-renderer=pdftocairo option was not established, as expected, during the original installation, by the printer-driver-cups-pdf.postinst script.  I wonder if, somehow, the old PDF queue was not fully removed when I removed the old printer-driver-cups-pdf (2.6.1-22) package.

Anyhow, thanks for the help.

Best regards,

--Neil Ormos