| Summary: | KPrinter fails to parse PPDs and shows incorrect printer options, but CUPS itself works correctly with same PPDs | ||
|---|---|---|---|
| Product: | [Unmaintained] kdeprint | Reporter: | Andreas Koch <ahk> |
| Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | major | CC: | cimmino.marco, jlayt |
| Priority: | HI | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
PPD HP LaserJet 2430 DTN
Screen capture of incorrect KPrinter properties dialog PPD for Lexmark Optra T610n printer, works in CUPS but fails in KDEPrint |
||
Created attachment 19826 [details]
PPD HP LaserJet 2430 DTN
Created attachment 19827 [details]
Screen capture of incorrect KPrinter properties dialog
I confirm this bug. I recently experienced a similar situation, but had no time to investigate further. (And right now I've neither time [or even a Linux PC system] to do so.) If this is now biting other users as well, this is a serious problem. (I initially thought it may be only a local problem of the box I was using at the time.) ---------- [AFAIK, KDEPrint does not use the CUPS API to parse the PPDs; it does "its own thing", but I can't remember the details.] Additional thought: HP have submitted their "For Macintosh only"-tagged PPDs to Linuxprinting.org since some time already. They seem to work just fine for CUPS/Linux too, but nevertheless I mildly complained, because they may lead to user confusion. They also contain some Apple-specific statements and paths [which normally should be ignored by any PPD-processing application if they don't understand them]. Now I wonder if this could contribute to this bug? Andreas, can you check if this is the case (that all failing PPDs in KDEPrint are "For Macintosh only" ones)? No, a PPD for a a Lexmark Optra T610n PostScript laser printer shows the same symptoms. For reference, I also attach that PPD, which works perfectly in CUPS. So the problem appears to extend beyond any possible Mac-isms in the HP PPDs. Created attachment 19840 [details]
PPD for Lexmark Optra T610n printer, works in CUPS but fails in KDEPrint
The erroneous behavior reported here appears to be due to a -O3 optimization problem in GCC 4.1.1 (specifically, the Gentoo ebuild gcc-4.1.1-r3). When compiling kdelibs and kdebase with -O2 instead, KDEPrint does parse the PPDs successfully (kprinter doesn't output a warning), and shows the correct printer options in the Properties dialog. Andreas why you have closed the bug? Bug appears also in Kubuntu Feisty 7.04 for a lot of people and for a lot of variety of printers, like me with all canon pixma ip family. All is compiled with gcc 4.1.2 but don't know if flag -O3 is responsible or not. Closing as worksforme doesn't help us. https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/99372 > Andreas why you have closed the bug?
Cimmo,
in our case, the optimization level definitely made the difference. On the new system described above, switching from -O3 to -O2 removed the error. Our older systems, which were compiled with -O2 right from the start, never showed the symptoms at all. So, at least in the case of the HP and Lexmark PPDs I used, KDEPrint itself seems innocent.
It is of course possible that other, actual errors show up for other PPDs, such as the Canon PPDs you mention. In that case, you should open a new bug report here (with a possible link to this report) and attach your PPDs.
Closing old Resolved status bug. |
Version: (using KDE KDE 3.5.5) Installed from: Compiled From Sources Compiler: gcc 4.1.1 OS: Linux Recent versions of KDEPrint appear to be no longer able to parse PPDs that were handled successfully before and continue to be processed successfully by CUPS 1.2.6. Applications such as kprinter output a message kdeprint: WARNING: PPD syntax error, PPD parse failed and then no longer show the correct options in the printer-specific options dialog. CUPS itself continues to handle these same PPDs correctly and processes the right options when printing from the command line. As an example, I attach a PPD for a HP LaserJet 2430 DTN PostScript printer. To demonstrate the problems, consider the selection of the paper input tray. The PPD defines the following trays, which are also recognized by lpoptions -l ... InputSlot/Media Source: *AutomaticallySelect Tray1 Tray2 Tray3_500 ... However, kprinter no longer shows these names in the Paper source property, but instead uses the (arbitrary?) names Upper Tray, Lower Tray, Multi-Purpose Tray and Large-Capacity Tray (see attached screenshot). Selecting one of these options has no effect, sheets are always pulled from the default defined in the PPD (Tray3_500). I have checked a few more reports in bugs.kde.org. Initially #100201 seemed to be most appropriate. However, that bugs states: ``More recent versions of CUPS have become more strict with PPD parsing. They wont any longer tolerate PPDs which dont comply with the Adobe PPD Specification.'' While cupstestppd does indeed find some errors in the PPD: /etc/cups/ppd/Tengwar.ppd: FAIL **FAIL** Bad Resolution choice 600x600x2dpi! REF: Page 84, section 5.9 WARN Line 491 only contains whitespace! WARN DefaultLeadingEdge has no corresponding options! WARN DefaultHalftoneType has no corresponding options! WARN Protocols contains PJL but JCL attributes are not set. REF: Pages 78-79, section 5.7. all options are shown correctly in the CUPS printer configuration page and command line printing from CUPS itself works _perfectly_. For example, to select the input source, lp -d tengwar -o media=tray2 test1.pdf does have the desired effect. So the difficulties appear to be at the KDE side of things. The same effect also occurs with other PPDs for the same printer (e.g., the one in the foomatic data base) or PPDs for different printers (e.g., one for a Lexmark Optra T610n printer, which also worked correctly in prior versions of KDE).