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.
** Package changed: ghostscript (Ubuntu) => foomatic-filters (Ubuntu)
** Changed in: foomatic-filters (Ubuntu)
Importance: Undecided => Medium
** Changed in: foomatic-filters (Ubuntu)
Status: Incomplete => In Progress
** Changed in: foomatic-filters (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
Process 'gs' begins taking 100% CPU and loading up vast amounts of RAM on CUPS
restart
https://bugs.launchpad.net/bugs/463059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs