[opensuse] Is there a printing expert in the house?
This is the second time I have sent this query, but have received no response. If nobody can help with it, I apologize for troubling the group with it. I am hoping that someone with insight into it overlooked it, thus the explicit appeal in the subject line. I won't send it again, of course, if nothing hapens this time. The problem that surfaced a couple of weeks ago, after the printer had been installed for months, and had been working well all that time. The printer is Brother HL-1250. It is on the network, connected through a H-P 175x external print server. The problem is that when I send it a print job, the job gets to the printer, the printer comes out of its standby mode and warms up, and sheets of paper come feeding out, but the job is not properly printed. Instead, there is only a bit of printing at the top before the page is ejected, following which another page comes out with the same printing at the top, and this can go on forever, or until I turn the printer off. The printing at the top is like so: %!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25 (I have compressed this horizontally, in order to avoid breaking lines. Actually, each of the second and third segments begins only just below the ending of the segment above, so that it is all spread across the top of the page.) I do not know why it speaks of Adobe 3.0. That has to be a remnant from something from long-ago in another OS. The CUPS page for this printer shows that this printer is: "idle, accepting jobs, published." The CUPS error log for the printing attempt is as follows: I [14/Feb/2008:20:12:28 +0200] Adding start banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Adding end banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Job 7 queued on "Brother" by "stan". I [14/Feb/2008:20:12:28 +0200] Started backend /usr/lib64/cups/backend/lpd (PID 6901) for job 7. I [14/Feb/2008:20:15:53 +0200] commptr="" I [14/Feb/2008:20:15:53 +0200] Started "/usr/lib64/cups/cgi-bin/printers.cgi" (pid=6982) I [14/Feb/2008:20:16:02 +0200] commptr="" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/cgi-bin/admin.cgi" (pid=6984) I [14/Feb/2008:20:16:02 +0200] commptr="1+0+4+requested-attributes=all" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/daemon/cups-deviced" (pid=6985) E [14/Feb/2008:20:16:04 +0200] [CGI] Can't find HylaFAX program /usr/sbin/sendfax I do not know what the line about HylaFAX is at the end. HylaFAX is not present at all on the machine, although it was for a time. The problem began well before I ever downloaded HylaFAX. Printing was fine until a few weeks ago. I do not remember anything that has happened since related to the printer or to printing. Does anything above ring a bell for anyone? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 16 February 2008 08:53, Stan Goodman wrote:
...
The problem that surfaced a couple of weeks ago, after the printer had been installed for months, and had been working well all that time.
The printer is Brother HL-1250. It is on the network, connected through a H-P 175x external print server.
A quick check on the Web suggests this is not a PostScript-capable printer. Perhaps the problem is in the stand-alone print server?
...
The printing at the top is like so:
%!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25
(I have compressed this horizontally, in order to avoid breaking lines. Actually, each of the second and third segments begins only just below the ending of the segment above, so that it is all spread across the top of the page.)
The print spooler is sending PostScript to the printer. Either the printer does not support it or the spooler is not sending the proper preamble to switch the printer from it's default language (probably PCL) to PostScript.
I do not know why it speaks of Adobe 3.0. That has to be a remnant from something from long-ago in another OS.
This is the software that generated the print job saying that it is encoded using PostScript Level 3.
The CUPS page for this printer shows that this printer is: "idle, accepting jobs, published."
The CUPS error log for the printing attempt is as follows:
I [14/Feb/2008:20:12:28 +0200] Adding start banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Adding end banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Job 7 queued on "Brother" by "stan". I [14/Feb/2008:20:12:28 +0200] Started backend /usr/lib64/cups/backend/lpd (PID 6901) for job 7. I [14/Feb/2008:20:15:53 +0200] commptr="" I [14/Feb/2008:20:15:53 +0200] Started "/usr/lib64/cups/cgi-bin/printers.cgi" (pid=6982) I [14/Feb/2008:20:16:02 +0200] commptr="" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/cgi-bin/admin.cgi" (pid=6984) I [14/Feb/2008:20:16:02 +0200] commptr="1+0+4+requested-attributes=all" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/daemon/cups-deviced" (pid=6985) E [14/Feb/2008:20:16:04 +0200] [CGI] Can't find HylaFAX program /usr/sbin/sendfax
I do not know what the line about HylaFAX is at the end. HylaFAX is not present at all on the machine, although it was for a time. The problem began well before I ever downloaded HylaFAX.
It seems like there's some serious malconfiguration in your printing system. You could start over and define a new printer configuration for this device?
...
-- Stan Goodman
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 16 February 2008 19:07:18 Randall R Schulz wrote:
On Saturday 16 February 2008 08:53, Stan Goodman wrote:
...
The problem that surfaced a couple of weeks ago, after the printer had been installed for months, and had been working well all that time.
The printer is Brother HL-1250. It is on the network, connected through a H-P 175x external print server.
A quick check on the Web suggests this is not a PostScript-capable printer.
I would be happy to get it to print the same files as it printed without complaint until a few weeks ago. What I have been trying to print are plain text files, e.g. from Kmail and Kwriter, and HTML files.
Perhaps the problem is in the stand-alone print server?
The problem appeared while I was still using a print server that has since malfunctioned under warranty, H-P has replaced it with a new one, and the behavior is the same. In other words, what you suggest would require that both devices have the same fault. Anything is possible, but that seems far fetched.
...
The printing at the top is like so:
%!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25
(I have compressed this horizontally, in order to avoid breaking lines. Actually, each of the second and third segments begins only just below the ending of the segment above, so that it is all spread across the top of the page.)
The print spooler is sending PostScript to the printer. Either the printer does not support it or the spooler is not sending the proper preamble to switch the printer from it's default language (probably PCL) to PostScript.
I do not know why it speaks of Adobe 3.0. That has to be a remnant from something from long-ago in another OS.
This is the software that generated the print job saying that it is encoded using PostScript Level 3.
Impossible. The only copy of Acroreader on the machine is v8. Acroreader v3 is antediluvian software, and has never been in this openSuSE v10.3 installation. To be certain of that, I have done <find -name "acro*>. .
The CUPS page for this printer shows that this printer is: "idle, accepting jobs, published."
The CUPS error log for the printing attempt is as follows:
I [14/Feb/2008:20:12:28 +0200] Adding start banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Adding end banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Job 7 queued on "Brother" by "stan". I [14/Feb/2008:20:12:28 +0200] Started backend /usr/lib64/cups/backend/lpd (PID 6901) for job 7. I [14/Feb/2008:20:15:53 +0200] commptr="" I [14/Feb/2008:20:15:53 +0200] Started "/usr/lib64/cups/cgi-bin/printers.cgi" (pid=6982) I [14/Feb/2008:20:16:02 +0200] commptr="" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/cgi-bin/admin.cgi" (pid=6984) I [14/Feb/2008:20:16:02 +0200] commptr="1+0+4+requested-attributes=all" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/daemon/cups-deviced" (pid=6985) E [14/Feb/2008:20:16:04 +0200] [CGI] Can't find HylaFAX program /usr/sbin/sendfax
I do not know what the line about HylaFAX is at the end. HylaFAX is not present at all on the machine, although it was for a time. The problem began well before I ever downloaded HylaFAX.
It seems like there's some serious malconfiguration in your printing system. You could start over and define a new printer configuration for this device?
Another possibility that suggests itself is that something is converting innocent plain-text files into Postscript on the way to the printer. It would have to be something old enough to remember Acroreader v3.0. Thank you.
Stan Goodman
Randall Schulz
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman a écrit :
Another possibility that suggests itself is that something is converting innocent plain-text files into Postscript on the way to the printer. It would have to be something old enough to remember Acroreader v3.0.
default linux printing is postscript, so to have postscript is quite normal. But if your printer is not postscript compatible, some filter don't work. did youbtry the most simple test, that is configuring with yast this printer under a new name?? you also mention the fact you installed hylafax, may be this install modifyed your printer setting given this is a network printer, can you test the printer from an other computer? if al this gives the same result, may be your printer was reset to a factory default (a power failure during night?) and you should watch at it's setup worth a try jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 16 February 2008 22:49:27 jdd wrote:
Stan Goodman a écrit :
Another possibility that suggests itself is that something is converting innocent plain-text files into Postscript on the way to the printer. It would have to be something old enough to remember Acroreader v3.0.
default linux printing is postscript, so to have postscript is quite normal.
But if your printer is not postscript compatible, some filter don't work.
did youbtry the most simple test, that is configuring with yast this printer under a new name??
I will do that first in the series of options that I now have after reading these responses.
you also mention the fact you installed hylafax, may be this install modifyed your printer setting
The problem appeared before I touched HylaFAX. Still, the fact that the error log mentions HulaFAX, when there is no HylaFAX on the machine at all is very suspicious.
given this is a network printer, can you test the printer from an other computer?
There is still an OS/2 installation on this very computer. The printer works with it as it should.
if al this gives the same result, may be your printer was reset to a factory default (a power failure during night?) and you should watch at it's setup
I'll think about that one.
worth a try jdd -- http://www.dodin.net
I never saw anyone wear a pistol belt with a bare midriff. =;-)8 Nice website. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-02-16 at 22:02 +0200, Stan Goodman wrote:
A quick check on the Web suggests this is not a PostScript-capable printer.
I would be happy to get it to print the same files as it printed without complaint until a few weeks ago. What I have been trying to print are plain text files, e.g. from Kmail and Kwriter, and HTML files.
Perhaps the problem is in the stand-alone print server?
The problem appeared while I was still using a print server that has since malfunctioned under warranty, H-P has replaced it with a new one, and the behavior is the same. In other words, what you suggest would require that both devices have the same fault. Anything is possible, but that seems far fetched.
Probably misconfigured.
The printing at the top is like so:
%!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25 ... from something from long-ago in another OS.
This is the software that generated the print job saying that it is encoded using PostScript Level 3.
Impossible. The only copy of Acroreader on the machine is v8. Acroreader v3 is antediluvian software, and has never been in this openSuSE v10.3 installation. To be certain of that, I have done <find -name "acro*>.
Adobe acroread is part of a typical opensuse install, and is certainly not antediluvian: cer@nimrodel:~> rpm -q -f `which acroread` acroread-7.0.9-59 What you are seen above is postscript, not pdf: don't confuse both. All linux printing is done as postscript (and version 3 is correct, and modern). When you print a plain text file it is typically converted to postscript first, then it is sent to the print server. This server must know it is postscript and treat is accordingly; in this case, convert postscript to whatever coding your printer really understands. You can try to print some other kind of files instead of text. ...
It seems like there's some serious malconfiguration in your printing system. You could start over and define a new printer configuration for this device?
Another possibility that suggests itself is that something is converting innocent plain-text files into Postscript on the way to the printer. It would have to be something old enough to remember Acroreader v3.0.
Not acrobat reader pdf: it is postscript version 3, which is correct. You can use version 1, 2, and 3, if I remember correctly. And yes, the correct thing in linux is to convert the plain text to ps, and send that to the print server. It is the print server fault. To send plain text as text I think you have to send it "raw". There may be some documentation about this in the cup's manual. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHt030tTMYHG2NR9URAuPFAJsE/3S5ShTYkwocQUaTrPLsk2XDhQCeLKcz 9eVJ93AOEGxU7daXmhgvwgU= =zTqa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 16 February 2008 22:56:18 Carlos E. R. wrote:
The Saturday 2008-02-16 at 22:02 +0200, Stan Goodman wrote:
A quick check on the Web suggests this is not a PostScript-capable printer.
I would be happy to get it to print the same files as it printed without complaint until a few weeks ago. What I have been trying to print are plain text files, e.g. from Kmail and Kwriter, and HTML files.
Perhaps the problem is in the stand-alone print server?
The problem appeared while I was still using a print server that has since malfunctioned under warranty, H-P has replaced it with a new one, and the behavior is the same. In other words, what you suggest would require that both devices have the same fault. Anything is possible, but that seems far fetched.
Probably misconfigured.
Yes. I now understand the way I have to go.
The printing at the top is like so:
%!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25
...
from something from long-ago in another OS.
This is the software that generated the print job saying that it is encoded using PostScript Level 3.
Impossible. The only copy of Acroreader on the machine is v8. Acroreader v3 is antediluvian software, and has never been in this openSuSE v10.3 installation. To be certain of that, I have done <find -name "acro*>.
Adobe acroread is part of a typical opensuse install, and is certainly not antediluvian:
Acroread v3.0 can be described as antediluvian. But you are right: it doesn't say "Acroread", only "Adobe", so I guess I misinterpreted what I saw.
cer@nimrodel:~> rpm -q -f `which acroread` acroread-7.0.9-59
Right. You have v7.x. What is here is v8.x. v3.0 is very old. But that seems to be irrelevant.
What you are seen above is postscript, not pdf: don't confuse both. All linux printing is done as postscript (and version 3 is correct, and modern). When you print a plain text file it is typically converted to postscript first, then it is sent to the print server. This server must know it is postscript and treat is accordingly; in this case, convert postscript to whatever coding your printer really understands.
AH! The conversion takes place in the print server, not in CUPS? Is that right? That doesn't seem right: where would it take place if this were not a network printer, but were connected directly to the computer, with no print server?
You can try to print some other kind of files instead of text.
I can try PDF or graphic files (JPEG, etc.).
It seems like there's some serious malconfiguration in your printing system. You could start over and define a new printer configuration for this device?
Another possibility that suggests itself is that something is converting innocent plain-text files into Postscript on the way to the printer. It would have to be something old enough to remember Acroreader v3.0.
Not acrobat reader pdf: it is postscript version 3, which is correct. You can use version 1, 2, and 3, if I remember correctly. And yes, the correct thing in linux is to convert the plain text to ps, and send that to the print server.
That's clear now. I misunderstood.
It is the print server fault.
To send plain text as text I think you have to send it "raw". There may be some documentation about this in the cup's manual.
I'll look into that too. Thanks.
-- Cheers, Carlos E. R.
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-02-16 at 23:25 +0200, Stan Goodman wrote:
AH! The conversion takes place in the print server, not in CUPS? Is that right? That doesn't seem right: where would it take place if this were not a network printer, but were connected directly to the computer, with no print server?
There are several conversions. First, whatever you want to print is converted to postscript. This can be done directly by the application, or by a component of cups. Then cups, if the printer understands postscript, sends it to the printer. If not, cups can convert to the language the printer understands. If it is a remote printer, cups sends the postscript print data to the remote server, who is responsible to send to the printer, converting the postscript to the printer language if necessary - and this last step is failing, as I understand it. There maybe a method to do the conversion locally, but that I don't know. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHt2VhtTMYHG2NR9URAno9AJ9/yBn0sW3XUDFUsa1ErQSsHgSwrQCeKEpE jYZpviRSAYVMzctLshNxeH8= =zU+X -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 17 February 2008 00:36:03 Carlos E. R. wrote:
The Saturday 2008-02-16 at 23:25 +0200, Stan Goodman wrote:
AH! The conversion takes place in the print server, not in CUPS? Is that right? That doesn't seem right: where would it take place if this were not a network printer, but were connected directly to the computer, with no print server?
There are several conversions.
First, whatever you want to print is converted to postscript. This can be done directly by the application, or by a component of cups. Then cups, if the printer understands postscript, sends it to the printer. If not, cups can convert to the language the printer understands.
If it is a remote printer, cups sends the postscript print data to the remote server, who is responsible to send to the printer, converting the postscript to the printer language if necessary - and this last step is failing, as I understand it.
There maybe a method to do the conversion locally, but that I don't know.
Is it possible that the problem involves Ghostscript? Is Ghostscript configurable? After a more relaxed inspection of the printer's specs, I see that it supports PCL6 (which I know is not Postscript). But I've sent off a query to Brother asking whether there is either a driver or a firmware update making Postscript support possible. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 01:33 +0200, Stan Goodman wrote:
Is it possible that the problem involves Ghostscript? Is Ghostscript configurable?
No. Yes. I don't think gs is the problem because your cups side is converting to postscript. You can check creating a local printer that prints to file (I think).
After a more relaxed inspection of the printer's specs, I see that it supports PCL6 (which I know is not Postscript). But I've sent off a query to Brother asking whether there is either a driver or a firmware update making Postscript support possible.
I think the problem is simply a bad configuration at the print server, or a configuration that cups on your machine doesn't handle well. It should not matter whether the remote printer understands postscript directly or not, as long as it's controlling server knows how to convert postscript to PCL6. Did you say the printer server model? Perhaps a web site I can look the specifications? I'm thinking that your print server simply sends what it gets from the network directly to the printer without treatment, and that is wrong for cups, but fine for windows. I explain: Windows works differently, because it sends native printer data. On a windows network the client machines have the printer driver convert gdi calls to printer output (PCL) locally, and this is sent to the printer, which can be local or remote. All clients must do the conversion locally. In linux the clients do no conversion to printer language: in all cases they send to the remote print server as postscript, and it is this remote server who converts to PCL (or whatever the printer understands). This is an improvement on (and a consequence of) the original method that required linux printers to understand postscript. See the difference? I believe you are a victim of this. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHt4WqtTMYHG2NR9URAkubAJ46dkZ7MGEdITMWnVC/2W9kgwfpMgCdGQUN xxgArUG8imlAzRiIjqngAfM= =1Hle -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I CAN PRINT! I did it by playing with the drivers in the CUPS interface. All is well. Thank you all for your efforts to educate me. I have learned much from the experience. You are a great and helpful bunch. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. a écrit :
If it is a remote printer, cups sends the postscript print data to the remote server, who is responsible to send to the printer,
yes converting the
postscript to the printer language if necessary
probably not - and this last step is
failing, as I understand it.
There maybe a method to do the conversion locally, but that I don't know.
if the print server is a computer, you can configure it to do the translation, but if it's a cheap hardware one, no it don't do any conversion other than connecting to the net a non-net capable printer most of the time, when yast configure a printer it asks to create a "local filter" and ask for printer make, so this is the place where conversion take place jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 09:28 +0100, jdd wrote:
if the print server is a computer, you can configure it to do the translation, but if it's a cheap hardware one, no it don't do any conversion other than connecting to the net a non-net capable printer
Yes, that's what I said on a later mail, more or less. It is not what cups expects, though.
most of the time, when yast configure a printer it asks to create a "local filter" and ask for printer make, so this is the place where conversion take place
Maybe this is what he did, he said he reconfigured it and it worked. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuB93tTMYHG2NR9URApmxAKCHLoDP3oz4L2MGVs4emSU5ejRDMgCfSzMz MzNPpyV+B943QC8shu9uAh0= =gcrv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 16 February 2008 12:02, Stan Goodman wrote:
On Saturday 16 February 2008 19:07:18 Randall R Schulz wrote:
On Saturday 16 February 2008 08:53, Stan Goodman wrote:
...
The printer is Brother HL-1250. It is on the network, connected through a H-P 175x external print server.
A quick check on the Web suggests this is not a PostScript-capable printer.
I would be happy to get it to print the same files as it printed without complaint until a few weeks ago. What I have been trying to print are plain text files, e.g. from Kmail and Kwriter, and HTML files.
Yes, but it certainly is a clue that PostScript is being sent to a printer that is not capable of interpreting PostScript.
Perhaps the problem is in the stand-alone print server?
The problem appeared while I was still using a print server that has since malfunctioned under warranty, H-P has replaced it with a new one, and the behavior is the same. In other words, what you suggest would require that both devices have the same fault. Anything is possible, but that seems far fetched.
I'm not saying print server has a problem, but rather that its configuration is the source or a contributing factor in the problem you're experiencing.
...
The printing at the top is like so:
%!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25
...
The print spooler is sending PostScript to the printer. Either the printer does not support it or the spooler is not sending the proper preamble to switch the printer from it's default language (probably PCL) to PostScript.
I do not know why it speaks of Adobe 3.0. That has to be a remnant from something from long-ago in another OS.
This is the software that generated the print job saying that it is encoded using PostScript Level 3.
Impossible. The only copy of Acroreader on the machine is v8. Acroreader v3 is antediluvian software, and has never been in this openSuSE v10.3 installation. To be certain of that, I have done <find -name "acro*>. .
Huh? I didn't say anything about Adobe Acrobat or Adobe Reader (of any version). I said the document being sent to the printer identifies itself as being PostScript Level 3. Adobe Acrobat and Adobe Reader _don't work with PostScript_, they work with PDF. PostScript and PDF, while related, are completely distinct things.
...
It seems like there's some serious malconfiguration in your printing system. You could start over and define a new printer configuration for this device?
Another possibility that suggests itself is that something is converting innocent plain-text files into Postscript on the way to the printer. It would have to be something old enough to remember Acroreader v3.0.
Again, Adobe Reader and / or Adobe Acrobat have _nothing to do with this_. And if some element of the print system believes the printer it is targeting is a PostScript printer, then naturally it is going to convert anything being printed on that device (from the the plainest of text to the fanciest of graphics-laden, typographically refined documents) into PostScript. That is how _all_ printing is done with PostScript printers. That's why I'm suggesting that something in your system has been mis-configured as if your Brother printer is a PostScript printer.
... Stan Goodman
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 16 February 2008 23:06:58 Randall R Schulz wrote:
On Saturday 16 February 2008 12:02, Stan Goodman wrote:
On Saturday 16 February 2008 19:07:18 Randall R Schulz wrote:
On Saturday 16 February 2008 08:53, Stan Goodman wrote:
...
The printer is Brother HL-1250. It is on the network, connected through a H-P 175x external print server.
A quick check on the Web suggests this is not a PostScript-capable printer.
I would be happy to get it to print the same files as it printed without complaint until a few weeks ago. What I have been trying to print are plain text files, e.g. from Kmail and Kwriter, and HTML files.
Yes, but it certainly is a clue that PostScript is being sent to a printer that is not capable of interpreting PostScript.
Perhaps the problem is in the stand-alone print server?
The problem appeared while I was still using a print server that has since malfunctioned under warranty, H-P has replaced it with a new one, and the behavior is the same. In other words, what you suggest would require that both devices have the same fault. Anything is possible, but that seems far fetched.
I'm not saying print server has a problem, but rather that its configuration is the source or a contributing factor in the problem you're experiencing.
...
The printing at the top is like so:
%!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25
...
The print spooler is sending PostScript to the printer. Either the printer does not support it or the spooler is not sending the proper preamble to switch the printer from it's default language (probably PCL) to PostScript.
I do not know why it speaks of Adobe 3.0. That has to be a remnant from something from long-ago in another OS.
This is the software that generated the print job saying that it is encoded using PostScript Level 3.
Impossible. The only copy of Acroreader on the machine is v8. Acroreader v3 is antediluvian software, and has never been in this openSuSE v10.3 installation. To be certain of that, I have done <find -name "acro*>. .
Huh? I didn't say anything about Adobe Acrobat or Adobe Reader (of any version). I said the document being sent to the printer identifies itself as being PostScript Level 3.
Right. I saw "Adobe", jumped to a conclusion, and interpreted it as the reader. Unforgivable, but I understand it now.
Adobe Acrobat and Adobe Reader _don't work with PostScript_, they work with PDF. PostScript and PDF, while related, are completely distinct things.
...
It seems like there's some serious malconfiguration in your printing system. You could start over and define a new printer configuration for this device?
Another possibility that suggests itself is that something is converting innocent plain-text files into Postscript on the way to the printer. It would have to be something old enough to remember Acroreader v3.0.
Again, Adobe Reader and / or Adobe Acrobat have _nothing to do with this_.
And if some element of the print system believes the printer it is targeting is a PostScript printer, then naturally it is going to convert anything being printed on that device (from the the plainest of text to the fanciest of graphics-laden, typographically refined documents) into PostScript. That is how _all_ printing is done with PostScript printers.
That's why I'm suggesting that something in your system has been mis-configured as if your Brother printer is a PostScript printer.
... Stan Goodman
Randall Schulz
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman schreef:
This is the second time I have sent this query, but have received no response. If nobody can help with it, I apologize for troubling the group with it. I am hoping that someone with insight into it overlooked it, thus the explicit appeal in the subject line. I won't send it again, of course, if nothing hapens this time.
The problem that surfaced a couple of weeks ago, after the printer had been installed for months, and had been working well all that time.
The printer is Brother HL-1250. It is on the network, connected through a H-P 175x external print server.
The problem is that when I send it a print job, the job gets to the printer, the printer comes out of its standby mode and warms up, and sheets of paper come feeding out, but the job is not properly printed. Instead, there is only a bit of printing at the top before the page is ejected, following which another page comes out with the same printing at the top, and this can go on forever, or until I turn the printer off.
The printing at the top is like so:
%!PS-Adobe-3.0 %%BoundingBox: 0 0 420 595 %%HiResBoundingBox: 0 0 419.55 595.25
(I have compressed this horizontally, in order to avoid breaking lines. Actually, each of the second and third segments begins only just below the ending of the segment above, so that it is all spread across the top of the page.)
I do not know why it speaks of Adobe 3.0. That has to be a remnant from something from long-ago in another OS.
The CUPS page for this printer shows that this printer is: "idle, accepting jobs, published."
The CUPS error log for the printing attempt is as follows:
I [14/Feb/2008:20:12:28 +0200] Adding start banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Adding end banner page "none" to job 7. I [14/Feb/2008:20:12:28 +0200] Job 7 queued on "Brother" by "stan". I [14/Feb/2008:20:12:28 +0200] Started backend /usr/lib64/cups/backend/lpd (PID 6901) for job 7. I [14/Feb/2008:20:15:53 +0200] commptr="" I [14/Feb/2008:20:15:53 +0200] Started "/usr/lib64/cups/cgi-bin/printers.cgi" (pid=6982) I [14/Feb/2008:20:16:02 +0200] commptr="" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/cgi-bin/admin.cgi" (pid=6984) I [14/Feb/2008:20:16:02 +0200] commptr="1+0+4+requested-attributes=all" I [14/Feb/2008:20:16:02 +0200] Started "/usr/lib64/cups/daemon/cups-deviced" (pid=6985) E [14/Feb/2008:20:16:04 +0200] [CGI] Can't find HylaFAX program /usr/sbin/sendfax
I do not know what the line about HylaFAX is at the end. HylaFAX is not present at all on the machine, although it was for a time. The problem began well before I ever downloaded HylaFAX.
Printing was fine until a few weeks ago. I do not remember anything that has happened since related to the printer or to printing.
Does anything above ring a bell for anyone?
Hi Stan, I am not the expert you asked for but I can tell you whats happening. What you see is the raw postscript output (the first line is always %!PS-Adobe) Print output in unix/linux is always postscript. You don't have a postscript printer so cups hat to translate the output to printer specific-output. This doesn't happen, so there should be something wrong in the printersetting in cups. Maybe you have selected a postscript version of you printer or so. Soo long, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
Hans defaber -
jdd -
Randall R Schulz -
Stan Goodman