PDA

View Full Version : PDF Printer



Gondarc
11-20-2011, 09:43 PM
Trying to install a PDF printer on an HD install of 6.7.1 using cups-pdf. Package installed and the CUPS printer config finds the virtual printer, but when trying to add the printer, it insists on asking for a model name, which is inapplicable; or a PPD file, which I cannot find.

How do I complete the Add Printer operation, please?

klaus2008
11-21-2011, 06:43 PM
When I installed the package cups-pdf (cups-pdf_2.5.0-16_i386.deb) using apt-get the new printer was installed automatically. The printer queue has the name PDF.
If you need a ppd file you can search the list of files included in the cups-pdf package. Open an LXTerminal and issue
dpkg -L cups-pdf | grep ppdIf the printer was installed properly then you should find the printer "Generic CUPS-PDF Printer (en)" in the "Generic" section.

Gondarc
11-21-2011, 07:31 PM
OK, I am so used to not finding the cups-pdf package in a distro package lists and having to do it directly through apt-get ... I removed cups-pdf with apt-get (it had not properly configured) and reinstalled it via synaptic ... this time it configured correctly ... except that I cannot get the CUPS printer manager screen to generate a test page ... selecting the option does nothing ... but a print from Libre Office works ... I find a PDF printer very useful for on-line receipts and orders (Amazon, Ebay, etc.) ... paperless office, Hah!

Gondarc
11-22-2011, 02:38 PM
Further ... having got the PDF printer working on the HD install, I tried the same on the live USB, using synaptic ... same initial problem, no printer in the printer manager list ... reinstalled with synaptic and I noticed that the "configuring cups-pdf" stage in the reinstall took much longer than on the first install, as it had with the HD Knoppix install ... and this time, again, the PDF printer appears in the lists and works ... still cannot get the "Print Test Page" function to do anything, though.

It appears that in order to get the package to be correctly configured with Knoppix 6.7.1, you have to install and then reinstall cups-pdf ... something in the configuration is missed on the first attempt that is picked-up on the reinstall. Weird ... interesting, but weird!

klaus2008
11-22-2011, 06:19 PM
... except that I cannot get the CUPS printer manager screen to generate a test page ... selecting the option does nothing ...I made the experience that I must start iceweasel and enter the address http://localhost:631/ instead of http://127.0.0.1:631/ if I want to print a test page. The file Test_Page.pdf can be found in the directory /var/spool/cups-pdf/ANONYMOUS/.

Werner P. Schulz
11-22-2011, 08:21 PM
..enter the address http://localhost:631/ instead of http://127.0.0.1:631/ if..Curious, don't you have the line


127.0.0.1 Microknoppix Knoppix localhost.localdomain localhostwithin your '/etc/hosts'?

Gondarc
11-22-2011, 11:07 PM
Curious, don't you have the line


127.0.0.1 Microknoppix Knoppix localhost.localdomain localhostwithin your '/etc/hosts'?

I do ... but I have just checked both ways of accessing the CUPS page directly from Iceweasel, and http://localhost:631/ works where http://127.0.0.1:631/ (as used by the printer manager access from "Preferences") does not ... as you say ... curious!

Gondarc
11-23-2011, 09:57 AM
Further ... equally curious ... documents created via cups-pdf are usually placed in a PDF directory that must be created in the user home directory ... in the case of Knoppix this is /home/knoppix/PDF ... documents printed using the this printer (such as from Libre Office) appear here on my system ... but the test pages generated by the button that works only in http://localhost:631/ do not appear anywhere ... they are in the jobs listed for the printer, but not the destination directory.

klaus2008
11-23-2011, 10:23 AM
I found the file Test_Page.pdf in the directory /var/spool/cups-pdf/ANONYMOUS/.

Gondarc
11-23-2011, 06:24 PM
Aha ... there it be ... the job queue did list it as generated by anonymous, so that makes some sense ... my original search failed because I did not use capitals in an implicit search string ... hey, ho!