Bug#712512: HL1250 PJL problems
After a long delay, I have found a little time to investigate further.
If I create two text files test1.txt and test2.txt containing the single
words ONE and TWO respectively, then the problem does not occur if I
print them in sequence:
lpr test1.txt ; lpr test2.txt
If I convert them to postscript using enscript:
enscript -p test1.ps test1.txt
and likewise for test2.ps
and use
lpr test1.ps; lpr test2.ps
then the error shows up. The first test1.ps is printed correctly, but
the second is not: it prints the usual PJL commands.
Maybe the PCL stream for test1.ps is not terminated properly, or the
UEL "<esc>%-12345X" is somehow corrupted. I see a
#define UEL "\033%-12345X"
in ghostscript-6.30-hl1250-patch-0.3.gz. But that patch is 14 years old
and I have used ghostscript directly with the hl1250 before using cups
with no problems. I intend to experiment with the current ghostscript
to see if the problem shows up there. But I need to refresh my mind
about raw postscript first.
Meanwhile I am attempting to capture the raw data sent to the printer as
described in https://wiki.ubuntu.com/DebuggingPrintingProblems. However
I am having trouble getting the output into a file.
lpadmin -p test -v file:/tmp/printout ...
does not seem to create the /tmp/printout. I tried -v
file:///tmp/printout after consulting the lpadmin man page.
The print jobs succeed, but no such file is created and so far I can't
find where the output has gone...
The http://localhost:631/ interface shows a "Connection:
file:///tmp/printout" or file:/tmp/printout in each case and shows
the test jobs as complete.
This is just an interim report. Until I solve the print-to-file
configuration, I don't think that I will make much progress.
FileDevice Yes is set in cups-files.conf.
ael
Reply to: