Felix, First of all, (and I may have told you this before, but I would like it recorded in this, and all relevant bugs): this is *not* a bug with the Ghostscript Postscript output. The GS Postscript is valid - we spent a lot of time confirming that when these bugs started to come to light. The fault is with the printer, and the problem really should be reported to Kyocera. Even if they can't fix it in printers "in the field" they should be able to debug the problem "directly" on the printer, rather than the kind of arm's length "reverse engineering" we'll have to undertake.
If we're going to track down the problem it will probably involve many interations of me "instrumenting" the Postscript file, you running the revised PS, and telling me the result. However, based on past experience, tells me to look at compression filters first, and the only one left in there was LZW. So, as a first punt, can you try: http://www.ghostscript.com/~chrisl/nolzw.ps IMPORTANT: it must be send directly to the printer (not opened in evince or other viewer, and printed from there - that would lose all my changes!). So you need to use: lpr -P <printer name> -oraw nolzw.ps There is also a method using netcat but I cannot remember the details...... If you can try that, and let us know the result. Thanks, Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
