By testing with a similar driver ("foo2zjs" on the HP LaserJet 1020) I could see how the problem got caused. The driver requires incoming PDF being converted to PostScript and instead of using the desired call of Poppler's pdftops it used an awkward Ghostscript call which is only supported as a fallback. I have fixed this in the upstream BZR repository of foomatic-filters now. I will tell when the package for Lucid is ready and ask you to test a Lucid live CD again then.
In general the following classes of printers are covered by this fix: All printers with "Foomatic/foo2..." drivers, all printers with "Foomatic/Postscript" drivers, PostScript printers from Ricoh and OEM.
For printers using "Foomatic/pxl...." drivers you can already test a Lucid live CD now, as Lucid's Ghostscript has a possible fix for these printers.
By testing with a similar driver ("foo2zjs" on the HP LaserJet 1020) I could see how the problem got caused. The driver requires incoming PDF being converted to PostScript and instead of using the desired call of Poppler's pdftops it used an awkward Ghostscript call which is only supported as a fallback. I have fixed this in the upstream BZR repository of foomatic-filters now. I will tell when the package for Lucid is ready and ask you to test a Lucid live CD again then.
In general the following classes of printers are covered by this fix: All printers with "Foomatic/foo2..." drivers, all printers with "Foomatic/ Postscript" drivers, PostScript printers from Ricoh and OEM.
For printers using "Foomatic/pxl...." drivers you can already test a Lucid live CD now, as Lucid's Ghostscript has a possible fix for these printers.