Intrepid, print broken with Minolta PagePro 8L printer

Lars, the PJL code of the option "PCL600" in this PPD file

http://openprinting.org/ppd-o-matic.cgi?driver=ljet2p&printer=Minolta-PagePro_8L&show=1

is not inserted in the output. There does not appear any PJL in the output. You can reproduce it with

cupsctl FileDevice=yes
cupsctl LogLevel=debug
lpadmin -p m -E -v /tmp/printout -m foomatic:Minolta-PagePro_8L-ljet2p.ppd -o PageSize=A4
lpr -P m ~/walking-map-portland-1.pdf
sudo less /tmp/printout

Note that the option is a so-called "hidden" option which does not appear in GUIs. It has only one choice, as it serves only for inserting a constant expression into the output. The insertion of this PJL code is needed so that the Minolta PagePro 8L prints with 600 dpi. See the entry on OpenPrinting:

http://openprinting.org/show_printer.cgi?recnum=Minolta-PagePro_8L

and also the output which you get with foomatic-rip 3.x.

stek79, please use Gutenprint for the time being, until the problem is fixed. Please tell also which driver of the two is actually the better one, so that I can choose best "recommended" driver after the fix.

stek79, can you please also check whether you can print with 600 dpi with Gutenprint? Gutemp[rint is set to 300 dpi by default and this can be the reason why it prints out-of-the-box.

Guys,
     first of all many thanks for the prompt reply, you are GREAT!

Yes, I'll stay with Gutenprint driver. I was wondering myself too which one is best, if there are differences at all.

Up to now I've printed only some openoffice letters and test pages, it seems they are equivalent - with Hardy I've always used foomatic.

I'll try your suggestion in a moment, let me try and I'll back with the result.

Thanks again!

 Ok guys,
        the resolution seems to be the culprit.

Gutenprint driver can't do 600DPI, max is 300.

I've tried to print with foomatic @ 300DPI, and guess what? It prints ok. Going back to 600DPI, the problem comes back.

So this is the problem, you were right!

BTW guys, with Intrepid I no longer see the print icon into the tray bar during printing, is this a known issue or I have to open a separate bug?

Thanks, you're GREAT!

Regarding which is better,
       I can now say that the default recommendation is right, since foomatic can actually do 600DPI, whereas Gutenprint doesn't go beyond 300.

Fixed in upstream BZR repository.

Thans Tim,
         when we will be able to have this change applied to ubuntu?

If you need any testing, just le me know!

Thanks again.

This bug was fixed in the package foomatic-filters - 4.0.0-0ubuntu1

---------------
foomatic-filters (4.0.0-0ubuntu1) jaunty; urgency=low

  * New upstream release (4.0.0 final release, BZR rev 195)
     - Let custom JCL options get correctly inserted.
     - Treat "None" as empty string in string and password options.
     - String and password option settings got inserted with the
       "Custom." prefix.
     - Fixed seghfault which occured when using string options.
     - Make foomatic-rip working correctly with PostScript of StarOffice 8
     - The PostScript code of PostScript options did not get inserted when
       the spooler is CUPS and foomatic-rip had to convert incoming PDF to
       PostScript (LP: #299918)
     - Made merging of PJL options of the PPD and of the driver correctly
       working.
     - Corrected the insertion of the "%%PageSetup" sections.
     - Inserted PostScript option settings from pstops were not corrected
       with custom option settings done on the command line (numerical,
       string, password).
     - If there was only one PJL option in the PPD no PJL got added at all
       (LP: #303691).
     - Made foomatic-rip conforming with the LSB compliance tests (LSB bug
       #2423).
     - Fixed infinite loop when page-specific option settings are used.
     - Made foomatic-rip correctly working with custom JCL options.
     - Option setting insertions got corrupted when there is a composite
       option in the PPD file (Upstream bug #173, comment #23).

 -- Till Kamppeter <email address hidden> Thu, 15 Jan 2009 10:39:49 +0100

Great work Tim!

I'm looking forward to try it in Intrepid.

Thanks guys!

2009/1/15 Launchpad Bug Tracker <email address hidden>

> This bug was fixed in the package foomatic-filters - 4.0.0-0ubuntu1
>
> ---------------
> foomatic-filters (4.0.0-0ubuntu1) jaunty; urgency=low
>
> * New upstream release (4.0.0 final release, BZR rev 195)
> - Let custom JCL options get correctly inserted.
> - Treat "None" as empty string in string and password options.
> - String and password option settings got inserted with the
> "Custom." prefix.
> - Fixed seghfault which occured when using string options.
> - Make foomatic-rip working correctly with PostScript of StarOffice 8
> - The PostScript code of PostScript options did not get inserted when
> the spooler is CUPS and foomatic-rip had to convert incoming PDF to
> PostScript (LP: #299918)
> - Made merging of PJL options of the PPD and of the driver correctly
> working.
> - Corrected the insertion of the "%%PageSetup" sections.
> - Inserted PostScript option settings from pstops were not corrected
> with custom option settings done on the command line (numerical,
> string, password).
> - If there was only one PJL option in the PPD no PJL got added at all
> (LP: #303691).
> - Made foomatic-rip conforming with the LSB compliance tests (LSB bug
> #2423).
> - Fixed infinite loop when page-specific option settings are used.
> - Made foomatic-rip correctly working with custom JCL options.
> - Option setting insertions got corrupted when there is a composite
> option in the PPD file (Upstream bug #173, comment #23).
>
> -- Till Kamppeter <email address hidden> Thu, 15 Jan 2009
> 10:39:49 +0100
>
> ** Changed in: foomatic-filters (Ubuntu)
> Status: In Progress => Fix Released
>
> --
> Intrepid, print broken with Minolta PagePro 8L printer
> https://bugs.launchpad.net/bugs/303691
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "foomatic-filters" source package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: foomatic-db
>
> Hi,
> with Intrepid I can no longer print correctly with the said printer.
>
> In particular, what happens is that the page is printed, but the margins
> are wrong. It seems that the page is printed with zoom, the fonts are huge
> and the page does not fit the paper. Printing for example the ubuntu test
> page, I see the top left corner aligned correctly, but I cannot see the
> other three corners since the page is like zoomed. On the top right corner,
> I see the ubuntu logo, and on the right paper edge I see the 50% label of
> the various colors.
>
> One important fact I discovered is that this happens with the recommented
> driver, which is Foomatic/ljet2p. If I choose the other avalable driver,
> which is CUPS+Gutenprint v5.2.0-rc1, the printing is correct!
>
> Let me know if you need other info to track this down. Basically a single
> test page print should be enough to determine if the bug is solved, since
> currently the printed page doesn't fit the corners at all.
>
> pier@pier-laptop:...

Due to the many regression bugs which the foomatic-filters package in Intrepid has (see changelog below) I propose to replace Intrepid's foomatic-filters by the final 4.0.0 release (which is currently in Jaunty).

An SRU request is uploaded to -proposed. Here is the debdiff

http://launchpadlibrarian.net/21399871/foomatic-filters_4.0.0%7Ebzr177-0ubuntu1_4.0.0-0ubuntu0.1.debdiff

Note that its is long, as due to the final release also the documentation is updated and the machine-generated files of the build system got regenerated. The following diff contains only the changes in active code (which actually modify the /usr/bin/foomatic-rip executable):

http://launchpadlibrarian.net/21399918/foomatic-4-intrepid-foomatic-4-final-changes-in-active-code.diff

The following debian/changelog contains all fixes on active code, the upstream ChangeLog I do not show here as it is much longer due to the documentation changes and the 4.0.0 final release.

foomatic-filters (4.0.0-0ubuntu0.1) intrepid-proposed; urgency=low

  * New upstream release (4.0.0 final release, BZR rev 195, all the changes
    against rev 177 as shipped by Intrepid are regressions against Hardy)
     - Let custom JCL options get correctly inserted.
     - Treat "None" as empty string in string and password options.
     - String and password option settings got inserted with the
       "Custom." prefix.
     - Fixed segfault which occured when using string options (LP: #318614).
     - Make foomatic-rip working correctly with PostScript of StarOffice 8.
     - The PostScript code of PostScript options did not get inserted when
       the spooler is CUPS and foomatic-rip had to convert incoming PDF to
       PostScript (LP: #299918).
     - Made merging of PJL options of the PPD and of the driver correctly
       working (LP: #318818).
     - Corrected the insertion of the "%%PageSetup" sections (LP: #318818).
     - Inserted PostScript option settings from pstops were not corrected
       with custom option settings done on the command line (numerical,
       string, password).
     - If there was only one PJL option in the PPD no PJL got added at all
       (LP: #303691).
     - Made foomatic-rip conforming with the LSB compliance tests (LSB bug
       #2423, LP: #318818).
     - Fixed infinite loop when page-specific option settings are used
       (LP: #318816).
     - Made foomatic-rip correctly working with custom JCL options.
     - Option setting insertions got corrupted when there is a composite
       option in the PPD file (Upstream bug #173, comment #23).

 -- Till Kamppeter <email address hidden> Mon, 19 Jan 2009 16:42:49 +0100

Accepted foomatic-filters into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Guys,
       yesterday I tested the new foomatic-filters, as per directions.

Too bad I have to tell you that my problem is still there.

Just to be more clear regarding the problem I'm experiencing, I've taken a picture with my phone of a test print page. You can find it attached.

Thanks again for the efforts, should you need other info to track this down, just let me know.

I have checked and there is also a problem in the /usr/lib/cups/filter/pdftopdf file.

Please do another test with a dummy pdftopdf filter:

sudo -s
mv /usr/lib/cups/filter/pdftopdf /usr/lib/cups/filter/pdftopdf.orig
cat > /usr/lib/cups/filter/pdftopdf << EOF
#!/bin/sh
cat \$6
EOF
chmod a+rx /usr/lib/cups/filter/pdftopdf
exit

Now send another print job. Does it come out correctly?

Note that with the dummy pdftopdf filter page management options (like 4 pages per sheet, scaling, selected pages, ...) will not work. Return to the normal pdftopdf with

sudo cp /usr/lib/cups/filter/pdftopdf.orig /usr/lib/cups/filter/pdftopdf

Adding cups task ... (the pdftopdf filter is part of the cups package).

You made it, Tim!

Now it prints beautifully!

Thank you very much guys, you are doing an incredible work!

Bye

:-)

It is confiurmed that the proposed SRU for foomatic-filters is fixing this problem for the foomatic-filters side.

In addition, a fix in the CUPS package is needed, as the pdftopdf CUPS filter emits the PDF output with a leading blank line which breaks the parsing by foomatic-rip. I have fixed this and uploaded the fix into the Debian BZR repository of CUPS, so that it will appear in the next Jaunty package.

I also want to propose an SRU for that fix, so that this bug gets also solved in Intrepid.

The debdiff of the SRU is attached.

There is an updated version which fixes a regression:

 foomatic-filters (4.0.0-0ubuntu0.2) intrepid-proposed; urgency=low
 .
   * debian/patches/foomatic-rip-segfault-on-jcl-merging.patch: Fixed
     segfault of the JCL merging process on long JCL command lists
     (LP: #321164). This was also reported on the Intrepid SRU
     4.0.0-0ubuntu0.1 in LP: #318614.

Can you please test this version instead/again, and report back here? Thank you!

Hi,
      I'll test it.

In every case, my problem is the pdftopdf file, which belongs to cups:

doni@sdoni-laptop-dev53:~$ dpkg -S /usr/lib/cups/filter/pdftopdf
cups: /usr/lib/cups/filter/pdftopdf

So in other words, I can't reproduce the bug fixed with this last release.

2009/1/30 Martin Pitt <email address hidden>

> There is an updated version which fixes a regression:
>
> foomatic-filters (4.0.0-0ubuntu0.2) intrepid-proposed; urgency=low
> .
> * debian/patches/foomatic-rip-segfault-on-jcl-merging.patch: Fixed
> segfault of the JCL merging process on long JCL command lists
> (LP: #321164). This was also reported on the Intrepid SRU
> 4.0.0-0ubuntu0.1 in LP: #318614.
>
> Can you please test this version instead/again, and report back here?
> Thank you!
>
> ** Tags added: verification-needed
>
> ** Tags removed: verification-done
>
> --
> Intrepid, print broken with Minolta PagePro 8L printer
> https://bugs.launchpad.net/bugs/303691
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "cups" source package in Ubuntu: In Progress
> Status in "foomatic-filters" source package in Ubuntu: Fix Released
> Status in cups in Ubuntu Intrepid: Triaged
> Status in foomatic-filters in Ubuntu Intrepid: Fix Committed
>
> Bug description:
> Binary package hint: foomatic-db
>
> Hi,
> with Intrepid I can no longer print correctly with the said printer.
>
> In particular, what happens is that the page is printed, but the margins
> are wrong. It seems that the page is printed with zoom, the fonts are huge
> and the page does not fit the paper. Printing for example the ubuntu test
> page, I see the top left corner aligned correctly, but I cannot see the
> other three corners since the page is like zoomed. On the top right corner,
> I see the ubuntu logo, and on the right paper edge I see the 50% label of
> the various colors.
>
> One important fact I discovered is that this happens with the recommented
> driver, which is Foomatic/ljet2p. If I choose the other avalable driver,
> which is CUPS+Gutenprint v5.2.0-rc1, the printing is correct!
>
> Let me know if you need other info to track this down. Basically a single
> test page print should be enough to determine if the bug is solved, since
> currently the printed page doesn't fit the corners at all.
>
> pier@pier-laptop:~$ lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> pier@pier-laptop:~$ apt-cache policy foomatic-db
> foomatic-db:
> Installato: 20080918-0ubuntu4
> Candidato: 20080918-0ubuntu4
> Tabella versione:
> *** 20080918-0ubuntu4 0
> 500 http://archive.ubuntu.com intrepid/main Packages
> 100 /var/lib/dpkg/status
> pier@pier-laptop:~$
>
>
> Thanks, and congrats on the great work!
> Go ubuntu!
>

stek79, the foomatic-filters SRU is only a regression test for you. Install it and see whether you still can print with my dummy pdftopdf installed. There will appear a new CUPS SRU soon. When you install it it will replace your dummy pdftopdf by a fixed pdftopdf. If you can print after that, the bug is completely fixed for you.

The CUPS SRU will also get announced here in this bug report.

Guys,
     I've tested the last foomatic-filters.

There is a problem, the output is a bit scrambled. Size is ok, but I find some weird chars at the top of the page, see attached pictures.

I have checked if the previous test page is ok (when I told you that it was printing correctly), but I found them here too. They are small, I missed them since I was mainly looking at the page size, which were ok.

I've tried to switch to the gutenprint drivers, just to see if they print correctly, and the do.

Can this be a problem of the dummy pdftopdf filter? I don't remember to have ever had such a problem, previously.

Thanks guys.

Even worst

I have checked on my machine (with fixed pdftopdf filter) and for me the output file looks correct (PJL syntax, PCL code). I attach one of my output files. Please send it to your printer unfiltered:

sudo -s
cat output.pcl > /dev/usblp0
exit

OR

sudo -s
cat output.pcl > /dev/lp0
exit

Are you sure that your paper was really blank before you have used it? If you send a text file unfiltered, does it produce readable text linmes on the paper? Are you also sure that the dummy pdftopdf filter is still in place?

Can you make a copy of your print queue (in system-config-printer right-click printer icon, choose "Copy", enter "debug" as name) and then do:

cupsctl LogLevel=debug
cupsctl FileDevice=yes
lpadmin -p debug -E -v /tmp/printout

then print a job to this queue and attach it to this bug report.

Can you also attach the /var/log/cups/error_log output of your print job?

Can you also tell me which platform (32-bit or 64-bit) you are using? Then I could attach for you a binary of the fixed pdftopdf.

Hello Tim,
       here are the results of your requests.

a) Attached you can find a picture of the print of your output file. As you can see, it is not correct:

1) there are those weird chars
2) it is not vertically centered

b) Yes, the paper I've used was blank

c) How can I print some straight text to the printer? I've tried something like:

cat /etc/hosts > /dev/lp0

but the printer keeps blinking with no printing at all

d) Yes, the pdftopdf is the dummy one. Here it is:

cat /usr/lib/cups/filter/pdftopdf
#!/bin/sh
cat $6

e) You can find in following attachments both the /tmp/printout and the error_log.

f) I'm using a 32 bit system

Thanks for the help.

Sorry Till,
      I keep messing with your name :(

/tmp/printout

cups error_log

Unfortunately, the error_log and the printout file are from your Gutenprint queue.

For me it also looks like that the problem is in the driver itself and not in foomatic-filters.

Can you please check the following:

1. With which driver do you suffer the problem of the strange characters? With Gutenprint or with ljet2p? If you observe it only with Gutenprint, foomatic-filters cannot be the culprit as it is not used by Gutenprint.

2. If you have the problem with ljet2p, can you try both 300 dpi and 600 dpi resolution? Does at least one of the two resolutions work? Which resolutions work?

3. If you have tracked down with which driver and with which option settings the problem occurs, redo the steps of my last posting with that queue and that settings.

Please do not compress files when you attach them. Thanks.

Can you also test whether your printer prints correctly (in 300 dpi) if you set up a print queue for a "Generic PCL 4 printer" with the ljet2p driver?

Till,
      sorry for the inconvenience.

I've redone all the tests. To be sure about the results, I've configured five queues with distinctive names:

- PagePro-8L-Gutenprint
- PagePro-8L-ljet2p-300
- PagePro-8L-ljet2p-600
- PCL-4-Printer
- debug (ljet2p, 600 DPI)

I can confirm you that the problem is with the PagePro-8L-ljet2p, both 600 DPI and 300. Printing with the 300 DPI resolution, actually there is only a small black square dot near the top left, but the page is not centered correctly. Gutenprint is and has always been ok.

Interesting news is that the PCL-4-Printer, with ljet2p, prints ok! Page well centered with no weird characters.

You can find attached the new error_log. The test print is the Job 80.

Also I attach the new printout, to the print debug.

One important note, perhaps I haven't been clear about this point previusly. The previous print pictures I attached (DSC0070-low) was a direct cat output.pcl > /dev/lp0 of YOUR output.pcl, and it was BROKEN too (as you can see).

Let me know if you want me to perform some other tests with the pdftopdf filter that you attached

stek79, thank you for the further investigations. I have found the problem. The mechanism to add PJL to a job corrupts the job data. This is a regression between Foomatic 3.0.x and 4.0.x, or between Hardy and Intrepid. None of the suggested SRUs fixes this, but the SRUs also do not add any further regression.

I have fixed this problem in foomatic-rip now, upstream, for Jaunty, and for Intrepid. A new Intrepid SRU will soon appear in -proposed (debdiff against the previous one is attached).

I also attach a 32-bit binary of the fixed foomatic-rip to replace your /usr/bin/foomatic-rip. Please also replace your /usr/lib/cups/filter/pdftopdf with the binary which I have posted with an earlier posting. Make sure that the two files are world-executable ("sudo chmod 755 ..."). Then you should be able to test immediately.

New version for Intrepid uploaded to -proposed. Can you please test it? Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

 foomatic-filters (4.0.0-0ubuntu3) intrepid-proposed; urgency=low

   * debian/patches/02-foomatic-rip-binary-data-after-pjl-options-corrupted.patch:
     Binary job data got corrupted after reading PJL options from the driver
     output. This should finally fix LP: #318614.

   * debian/patches/foomatic-rip-segfault-on-jcl-merging.patch,
     debian/patches/01-foomatic-rip-segfault-on-jcl-merging.patch: Renamed patch
     to make the patches getting applied in the correct order.

Till,
     I confirm you that now the printing is ok!

I've printed a test page along with another image, and they are ok.

Great work!

Consider this bug as successfully closed.

Thanks again.

stek79, thank you for confirming that all relevant bugs in foomatic-filters are now fixed.

The SRU on foomatic-filters is completed and verified now. The package can be moved to -updates.

Note that this bug report has still to be open as an SRU request for CUPS, as the proposed SRU with the fix in the pdftopdf filter has not yet arrived in -proposed. So, stek79, please stay tuned for the next CUPS upload into -proposed. We will inform you on this bug report and ask you test then to see whether the patch has really made it into the enew package and other fixes in it will not break your printing. Even if you are already able to print now with the new foomatic-filters and my pdftopdf binary, we will also need your confirmation on the new CUPS package. Thank you in advance.

Ok Till,
      I'm happy that we finally sorted this out!

Just let me know when the new packages will be ready, I'll be glad to test
them!

Have a nice week-end!

2009/2/6 Till Kamppeter <email address hidden>

> stek79, thank you for confirming that all relevant bugs in foomatic-
> filters are now fixed.
>
> The SRU on foomatic-filters is completed and verified now. The package
> can be moved to -updates.
>
> Note that this bug report has still to be open as an SRU request for
> CUPS, as the proposed SRU with the fix in the pdftopdf filter has not
> yet arrived in -proposed. So, stek79, please stay tuned for the next
> CUPS upload into -proposed. We will inform you on this bug report and
> ask you test then to see whether the patch has really made it into the
> enew package and other fixes in it will not break your printing. Even if
> you are already able to print now with the new foomatic-filters and my
> pdftopdf binary, we will also need your confirmation on the new CUPS
> package. Thank you in advance.
>
> --
> Intrepid, print broken with Minolta PagePro 8L printer
> https://bugs.launchpad.net/bugs/303691
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "cups" source package in Ubuntu: In Progress
> Status in "foomatic-filters" source package in Ubuntu: Fix Released
> Status in cups in Ubuntu Intrepid: In Progress
> Status in foomatic-filters in Ubuntu Intrepid: Fix Committed
>
> Bug description:
> Binary package hint: foomatic-db
>
> Hi,
> with Intrepid I can no longer print correctly with the said printer.
>
> In particular, what happens is that the page is printed, but the margins
> are wrong. It seems that the page is printed with zoom, the fonts are huge
> and the page does not fit the paper. Printing for example the ubuntu test
> page, I see the top left corner aligned correctly, but I cannot see the
> other three corners since the page is like zoomed. On the top right corner,
> I see the ubuntu logo, and on the right paper edge I see the 50% label of
> the various colors.
>
> One important fact I discovered is that this happens with the recommented
> driver, which is Foomatic/ljet2p. If I choose the other avalable driver,
> which is CUPS+Gutenprint v5.2.0-rc1, the printing is correct!
>
> Let me know if you need other info to track this down. Basically a single
> test page print should be enough to determine if the bug is solved, since
> currently the printed page doesn't fit the corners at all.
>
> pier@pier-laptop:~$ lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> pier@pier-laptop:~$ apt-cache policy foomatic-db
> foomatic-db:
> Installato: 20080918-0ubuntu4
> Candidato: 20080918-0ubuntu4
> Tabella versione:
> *** 20080918-0ubuntu4 0
> 500 http://archive.ubuntu.com intrepid/main Packages
> 100 /var/lib/dpkg/status
> pier@pier-laptop:~$
>
>
> Thanks, and congrats on the great work!
> Go ubuntu!
>

Hi Till,
      I've experienced twice an error during printing.

It is not a matter of image corruption, but in those times the printer did not print at all.

A small windows told me "too many failed attempts".

I attach the error_log, it seems to be a Bad Request problem.

Please note that they're pretty random. For example, now I've turned on the laptop to print a document. I got the error. Then I printed again, and it worked.

Can this be related to the applied changes? It looks like a different issue.

This bug was fixed in the package cups - 1.3.9-13

---------------
cups (1.3.9-13) unstable; urgency=low

  [ Till Kamppeter ]
  * debian/local/filters/pdf-filters/filter/imagetopdf.c: Added support for
    the new "fit-to-page" option (new, more intuitive name for "fitplot").
  * debian/filters/pstopdf: Only apply paper size if the "fitplot" or the
    "fit-to-page" option is set.
  * debian/local/filters/cpdftocps: Only the last digit of the number of
    copies was used (LP: #309314).
  * debian/local/filters/pdf-filters/pdftopdf/pdftopdf.cxx: Do not preceed the
    PDF output with a newline (LP: #303691). Only impose the page size from
    the PPD file to all pages if the "fitplot" or the "fit-to-page" option is
    set. This prevented from automatic paper tray switching to the correct paper
    sizes when a multiple-page-size document is printed (partial fix for
    LP: #310575).
  * debian/patches/pdftops-cups-1.4.dpatch: Updated from CUPS 1.4 SVN. Contains
    fixes for multiple-page-size document printing (partial fix for
    LP: #310575).
  * debian/patches/pdftops-dont_fail_on_cancel.dpatch: Removed, should be
    fixed in the new upstream version of pdftops.

  [ Martin Pitt ]
  * debian/patches/pdftops-cups-1.4.dpatch: Add definition of
    HAVE_PDFTOPS and CUPS_PDFTOPS, so that the filter actually gets
    again built with pdftops support. (Fixes Till's change from above).

 -- Martin Pitt <email address hidden> Mon, 16 Feb 2009 07:52:20 +0000

ste79, the problem of your last comment has probably nothing to do with these updates.

foomatic-filters copied to -updates.

Accepted cups into intrepid-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Upgraded cups, foomatic-filters was already ok.

Printing is correct now, thanks for the good work!

Bye

This bug was fixed in the package cups - 1.3.9-2ubuntu8

---------------
cups (1.3.9-2ubuntu8) intrepid-proposed; urgency=low

  * debian/local/filters/cpdftocps: Only the last digit of the number of
    copies was used (LP: #309314).
  * debian/patches/pdftops-cups-1.4.dpatch: Let the pdftops filter only emit
    PostScript level 2 and not level 3, as some PostScript printers have
    problems with PostScript level 3 from Poppler, even if they are level 3
    printers (LP: #277404).
  * debian/local/filters/pdf-filters/pdftopdf/pdftopdf.cxx: Do not preceed the
    PDF output with a newline (LP: #303691).

 -- Till Kamppeter <email address hidden> Fri, 13 Mar 2009 19:08:02 +0100