Installation of Kyocera Mita FS-1020D failes with error: There was an error during the CUPS operation: 'server-error-internal-error'

Fixed upstream in foomatic-db-engine BZR repositories: rev 241 in head and rev241 in 4.0.

This bug was fixed in the package foomatic-db-engine - 4.0.0-0ubuntu8

---------------
foomatic-db-engine (4.0.0-0ubuntu8) karmic; urgency=low

  * debian/patches/25_fix-driver-in-printer-xml-without-driver-xml.patch:
    If a printer XML entry has a driver in its driver list but for which
    there is no driver XML entry, this printer/driver combo was considered
    as producing a PPD because the driver is not in the list of drivers
    without command line prototype. This leads for example to non-working
    "Foomatic/Gutenprint" driver entries in the printer setup tools
    (LP: #373371).

 -- Till Kamppeter <email address hidden> Fri, 8 May 2009 12:47:49 +0200

I propose this fix also for a SRU for Jaumty. debdiff attached (fixes also bug 361772), package uploaded to -proposed and waits for approval.

To reproduce:

lpinfo -m | grep -i 1020D

shows a "Foomatic/gutenprint" line for the Kyocera FS-1020D and trying to generate this PPD with

/usr/lib/cups/driver/foomatic cat foomatic:Kyocera-FS-1020D-gutenprint.ppd

leads to an error. After applying the fix

lpinfo -m | grep -i 1020D

does not show this wrong entry any more.

Is this a regression? It's quite an intrusive patch, and doesn't look obvious, so I wonder about the importance of this SRU.

Note that the SRU contains the fixes for two bugs. The patch for this bug looks bigger than it really is as I have also updated the comments according to the changes. There are only 3 or 4 code lines which got changed.

Is this bug getting fixed by that release? When will we see it?

It would be sad if our entire office can't print pages. So they start hatin'. But luckily it's only me and my boss who is testing Jaunty, the others in Intrepid. :-)

Accepted foomatic-db-engine into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Works fine with foomatic-db-engine 4.0.0-0ubuntu6.1 from jaunty-proposed. SOLVED!

This bug was fixed in the package foomatic-db-engine - 4.0.0-0ubuntu6.1

---------------
foomatic-db-engine (4.0.0-0ubuntu6.1) jaunty-proposed; urgency=low

  * debian/patches/25_fix-driver-in-printer-xml-without-driver-xml.patch:
    If a printer XML entry has a driver in its driver list but for which
    there is no driver XML entry, this printer/driver combo was considered
    as producing a PPD because the driver is not in the list of drivers
    without command line prototype. This leads for example to non-working
    "Foomatic/Gutenprint" driver entries in the printer setup tools
    (LP: #373371).

  * debian/patches/20_fix-jcl-options-as-members-of-composite-options.patch:
    Upstream fix in the PPD generator: In Foomatic PPDs JCL options were
    broken when they where member options of a composite options. In addition
    to these options not being correctly applied this made them also be
    interpreted as a PostScript options which in turn made foomatic-rip
    converting PDF jobs to PostScript. This made some printers suffering
    LP: #361772 which usually is worked around by the PDF printing workflow.

 -- Till Kamppeter <email address hidden> Fri, 8 May 2009 12:57:49 +0200