Comment 34 for bug 42965

Till wrote:
> The best is to have a call of foomatic-cleanupdrivers in the post-install
> and post-uninstall scripts of all packages which contain Foomatic data,
> including foomatic-db itself.

I'm using Edgy 20060924 which uses dynamically generated PPDs now (since foomatic-db-engine 3.0.2-20060530-2ubuntu2).

There are some pseudo drivers in foomatic-db that are only used to list supported printers on the linuxprinting.org website. It is not possible to generate PPDs from these pseudo-drivers since there is no Ghostscript command line.

Adding a printer with a pseudo driver with gnome-cups-manager results in no printer being added and the user has no clue of what went wrong. This gives a very bad user experience.

It would be nice to have the fix you mentioned in Edgy to avoid this.