Note that a virgin (not treated by any patches or programs, like for
example foomatic-cleanupdrivers) Foomatic database can have driver
entries with empty command line. These are simply entries which do not
provide PPD files to be generated via foomatic-db-engine. Most important
type of such drivers are
- Native CUPS drivers: They bring their own PPDs, usually generated by CUPS DDK
- Drivers which bring their own Foomatic XML files: The driver XML file in
foomatic-db is only to make these drivers appear on the linuxprinting.org web
site.
- Drivers for which there is more than one driver XML file: In this case only
one of the XML files produces PPDs, the others only contain a text hint telling
which is the one producing PPDs.
As empty or missing driver command lines are legal in the Foomatic XML
data format, every program using Foomatic should be able to handle this.
All programs which come with Foomatic do so.
Printer setup tools should be able to cope with this, either by only
showing printer/driver combos for which a PPD can be generated (or is
ready-made in /usr/share/ppd) or by producing an error message if a bad
combo is selected.
I move this bug to foomatic-gui, as it seems that only this program
breaks on empty driver command lines. But please check also whether
other printer tools like, gnome-cups-manager, KDE Printing Manager, CUPS
web interface, ... have the same problem.
** Changed in: foomatic-db (Ubuntu)
Sourcepackagename: foomatic-db => foomatic-gui
Status: Fix Released => Needs Info
--
foomatic-db-gutenprint causes printer setup malfunctioning
https://launchpad.net/bugs/39744
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
