It seems that we have narrowed down the problem to be a bug in Kyocera's PostScript interpreter to make the printers incompatible with the PostScript output of Ghostscript's "ps2write" output device.
A simple modification on the PostScript solves the problem and you can easily test it. Take any Ghostscript-generated PostScript file which makes your Kyocera printer hanging, for example one of the files attached to this bug. Edit the file with a text editor like "gedit" adding the line
/bind {} bind def
right after the line
%!PS-Adobe-3.0
which should be at or at least near the beginning of the file. Now send the file to the printer again with "nc". It should print now.
I will modify the pdftops CUPS filter to insert said line into the PostScript output of Ghostscript if the printer is a Kyocera. This can slow down printing performance a bit but most important is to be able to print at all.
Note that this does not work for Brother printers and so does not fix bug 950713.
It seems that we have narrowed down the problem to be a bug in Kyocera's PostScript interpreter to make the printers incompatible with the PostScript output of Ghostscript's "ps2write" output device.
A simple modification on the PostScript solves the problem and you can easily test it. Take any Ghostscript- generated PostScript file which makes your Kyocera printer hanging, for example one of the files attached to this bug. Edit the file with a text editor like "gedit" adding the line
/bind {} bind def
right after the line
%!PS-Adobe-3.0
which should be at or at least near the beginning of the file. Now send the file to the printer again with "nc". It should print now.
I will modify the pdftops CUPS filter to insert said line into the PostScript output of Ghostscript if the printer is a Kyocera. This can slow down printing performance a bit but most important is to be able to print at all.
Note that this does not work for Brother printers and so does not fix bug 950713.