[Kde-print-devel] [Bug 127401] kdeprint: Catastrophe! - Print to File (PDF)
Kurt Pfeifle
pfeifle at kde.org
Tue Jan 9 05:06:16 CET 2007
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=127401
------- Additional Comments From pfeifle kde org 2007-01-09 05:04 -------
@ comment 1, for msp debian org:
Using this commandline, with the CUPS print client "lpr", addressing a printer named 'Print to File (PDF)' will for sure not work.
The 'Print to File (PDF)' is a "virtual printer", specific to KDE, and not known to CUPS at all, which uses Ghostscript to work. (It is even there if you switch to a different print subsystem, or if you un-install CUPS completely).
The 'lpr: Print to File (PDF): unknown printer' message is therefor to be expected.
If Debian packagers did introduce patches that do address this KDE virtual printer from a CUPS client, this is meant to fall flat on its face.
Pierre & msp debian org:
Please run the following commands and tell us their output:
which gs
gs -h|head
which ps2pdfwr
which ps2pdf
which ps2pdf12
which ps2pdf13
which ps2pdf14
Last, use Konqueror and kprinter to "Print to file (PostScript)". Then, run these commands in turn on the PostScript file that you just now created:
ps2pdfwr -dCompatibilityLevel=1.4 /path/to/print.ps ~/print14.pdf
ps2pdfwr -dCompatibilityLevel=1.3 /path/to/print.ps ~/print13.pdf
ps2pdfwr -dCompatibilityLevel=1.2 /path/to/print.ps ~/print12.pdf
Do all these commands succeed? Does one of these fail? If so, your Ghostscript version is b0rken.
If you discover one of the above commands working, then set the respective compatibility level in the "Print to file (PDF)" properties of the kprinter dialog and try printing the Groklaw page again...
If I don't hear back from you until Feb 1, 2007, I assume the bug isnt there any more and close the report.
Cheers,
Kurt
More information about the Kde-print-devel
mailing list