Opening the file in Document Viewer and printing it from there is
completely useless in context because it just goes through the CUPS
filters, which I specifically said we needed to avoid for this test.

Your original problem, as reported, came about as a result of changing
the CUPS Postscript generation from a Poppler based solution to a
Ghostscript based solution - this was done to allow future use of high
fidelity color reproduction, and some other features available in
Ghostscript that were not going to be available in Poppler in the near
future.

As often happens with such a change, a few teething troubles have come
up, hence Till allowed a fallback to the the Poppler tools while we work
through them.

The:
"lpadmin -p <printer> -o pdftops-renderer-default=pdftops"

setting is that fallback - it does not solve anything, at best it works
around the problem.

I am trying to establish what needs done to get the Ghostscript output
compatible with your printer, so sending a file to the printer via CUPS
with the poppler based filter in force does nothing to help me (or,
ultimately, yourself!).

*PLEASE*, when I give instructions for testing, do not ignore them - I
write them for a reason.......

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978120

Title:
  Toshiba Estudio 230 printer driver bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to