Re: can't print from acroread
Hi, everyone. The problem I was having mid March is finally solved. I started this thread on Mar 16 having the problem of, though being able to print fine from the command line, not being able to print internally from applications such as acroread. Though this problem (which appears to be related to the printer filter I was using with lprng) was never solved itself, I, for another reason, switched over to using the printer filter provided by a program called 'ifhp' which uses the lprng spooler. Other than simply being better than the filter I was using previously, it also magically fixed the problem I was having of not being able to print from within various applications. Possibly this may also help someone else experiencing similar problems. Paul -In response to your message- --received from Erdmut Pfeifer-- thanks for the clear report. From this debugging information and a quick look at the lprng source, I would say that the problem occurs while trying to fork/exec the so-called input filter, though I do not yet have a clear idea why it fails... The waitpid(2) call returns a -1, which indicates that the waitpid failed. Actually, there are three error/return codes involved here: the exit code of the waited-for child process (the filter), the return code of the waitpid function itself, and in case the latter returns -1, the errno being set by waitpid, which _might_ provide further details on what went wrong (not sure whether it really would in this case, though). Unfortunately, this error number doesn't seem to make it to the debugging logs (or else we should see another diff) -- the -1 appears to be propagated to the logs instead. Although it would generally be easy to add another printf() to the lprng code, outputting the errno, I assume that you would rather avoid having to recompile the code and having to make sure that the modified version gets installed in the appropriate place. I guess we should do things like these as a last resort only. Instead we might try to apply the same wrap a script-technique here as well, by substituting a script for the filter program run by lprng. The script could output a few interesting things like command line args, environment, the errno in question, etc. before/after running the filter... There is a faint hope that something will differ here... :) First, however, I'd like to take a look at the full logs available already, so feel free to send them to me privately. In particular, I'm not sure yet as to how the other diff (the fd-0..5 vs. fd-0..8 thing) is related to the waitpid error ocurring later on. Maybe that is the real place where things start to go wrong. The complete logs will make it easier to dig through the appropriate portions of the source. Also, I'd like to take a look at your printcap file (especially the if-specification which is in effect for the printer in question), so be sure to attach that as well. BTW, which printer are you using -- is it a native postscript printer, or are you using ghostscript as a filter? If you haven't done so already, you might also want to try to run your test script from the command line but in the background. This might help to rule out issues with a controlling terminal being required by the filter. Don't know why it would need one, but who knows ... just an idea. Erdmut PS: I cannot promise to be able to take a closer look at this immediately, but I _will_ as soon as time permits. After all, getting a deeper understanding of the lprng mechanics might help me to eventually solve a somewhat similar problem I'm experiencing myself sporadically ;)
Re: can't print from acroread
On Fri, Mar 23, 2001 at 01:20:10PM -0800, peanut butter wrote: (...) To really simplify things while exposing the basic problem, I saved the pdf from acroread as a postscript file. I then wrote one script that prints this postscript file with the lpr -D5 option saving the output to one file while recording the returned status from lpr to another. I then ran this exact same command once from the command line and once from within acroread. Now, mind you, the script accepts no input arguments . . . so the execution of the script is exactly the same, printing the exact same postscript file, while printing correctly from one execution (command line) yet not from the other (acroread). good idea... I can offer the full debug report from either or both runs to anyone who should care to view it/them but in attempt to keep things as concise as possible, just below is the segment from both reports where they begin to deviate. thanks for the clear report. From this debugging information and a quick look at the lprng source, I would say that the problem occurs while trying to fork/exec the so-called input filter, though I do not yet have a clear idea why it fails... The waitpid(2) call returns a -1, which indicates that the waitpid failed. Actually, there are three error/return codes involved here: the exit code of the waited-for child process (the filter), the return code of the waitpid function itself, and in case the latter returns -1, the errno being set by waitpid, which _might_ provide further details on what went wrong (not sure whether it really would in this case, though). Unfortunately, this error number doesn't seem to make it to the debugging logs (or else we should see another diff) -- the -1 appears to be propagated to the logs instead. Although it would generally be easy to add another printf() to the lprng code, outputting the errno, I assume that you would rather avoid having to recompile the code and having to make sure that the modified version gets installed in the appropriate place. I guess we should do things like these as a last resort only. Instead we might try to apply the same wrap a script-technique here as well, by substituting a script for the filter program run by lprng. The script could output a few interesting things like command line args, environment, the errno in question, etc. before/after running the filter... There is a faint hope that something will differ here... :) First, however, I'd like to take a look at the full logs available already, so feel free to send them to me privately. In particular, I'm not sure yet as to how the other diff (the fd-0..5 vs. fd-0..8 thing) is related to the waitpid error ocurring later on. Maybe that is the real place where things start to go wrong. The complete logs will make it easier to dig through the appropriate portions of the source. Also, I'd like to take a look at your printcap file (especially the if-specification which is in effect for the printer in question), so be sure to attach that as well. BTW, which printer are you using -- is it a native postscript printer, or are you using ghostscript as a filter? If you haven't done so already, you might also want to try to run your test script from the command line but in the background. This might help to rule out issues with a controlling terminal being required by the filter. Don't know why it would need one, but who knows ... just an idea. Erdmut PS: I cannot promise to be able to take a closer look at this immediately, but I _will_ as soon as time permits. After all, getting a deeper understanding of the lprng mechanics might help me to eventually solve a somewhat similar problem I'm experiencing myself sporadically ;) -- Erdmut Pfeifer science+computing ag -- Bugs come in through open windows. Keep Windows shut! --
Re: can't print from acroread
Ok, here's some preliminary information to this problem I'm still experiencing with a pdf not printing from the acroread application. Erdmut Pfeifer gave an excellent suggestion below to which I dedicated a few hours. In short: make a script that gets executed as the the print command from within acroread. The script ls's the temp file that acroread creates and sends to the print command, copies it to a non-automatically-deleted file, tries printing the temp file itself and catches the return code from lpr. Here's some inital results: The script works beautifully although the print fails just as well when executed by the script as when by a typical print command both from within acroread. Indeed the status of the failed print command is captured though only offering, in my knowledge, a very vague return status of 255. To un-vague-ify this as best I could, I made one significant addition to the script of adding the -D5 option of lpr to offer verbose debugging information. This finally starts to get me somewhere but not so far as to completely understand and solve the whatever's really going on. To really simplify things while exposing the basic problem, I saved the pdf from acroread as a postscript file. I then wrote one script that prints this postscript file with the lpr -D5 option saving the output to one file while recording the returned status from lpr to another. I then ran this exact same command once from the command line and once from within acroread. Now, mind you, the script accepts no input arguments . . . so the execution of the script is exactly the same, printing the exact same postscript file, while printing correctly from one execution (command line) yet not from the other (acroread). I can offer the full debug report from either or both runs to anyone who should care to view it/them but in attempt to keep things as concise as possible, just below is the segment from both reports where they begin to deviate. Notice in about the middle of the segments (sixth line), there is a line that reads . . . lpr lp: plp_waitpid: report . . . . In the bad report, report is followed by -1. In the good one, report is followed by the PID (what I suppose is a child process of lpr) mentioned on the line just before it. In the failed print case, things go bad from here onward and shortly end while things continue on another 80,000 lines or so in the successful print case. The unfortunate thing is that this doesn't tell me much. I'm hoping it may say something more to one of you likely more knowledgeable people on the list. --- lpr debug report from script when run from acroread --- . . . 2001-03-23-12:32:19.397 isengard [6420] lpr lp: Write_outbuf_to_OF: read status 0, read 0, '' 2001-03-23-12:32:19.397 isengard [6420] lpr lp: Write_outbuf_to_OF: no more reading 2001-03-23-12:32:19.397 isengard [6420] lpr lp: Write_outbuf_to_OF: waiting 0 secs for pid 6422, suspend 0 2001-03-23-12:32:19.398 isengard [6420] lpr lp: Wait_for_pid: name 'IF', pid 6422, suspend 0, timeout 0 2001-03-23-12:32:19.398 isengard [6420] lpr lp: plp_waitpid: pid 6422, options 2 2001-03-23-12:32:19.398 isengard [6420] lpr lp: plp_waitpid: report -1, status exit status 0 (JSUCC) 2001-03-23-12:32:19.398 isengard [6420] lpr lp: Wait_for_pid: pid -1 exit status 'exit status 0 (JSUCC)' 2001-03-23-12:32:19.398 isengard [6420] lpr lp: Wait_for_pid: returning 'UNKNOWN STATUS '-1'', exit status 'exit status 0 (JSUCC)' 2001-03-23-12:32:19.398 isengard [6420] lpr lp: setstatus: IF filter problems, error 'UNKNOWN STATUS '-1'' 2001-03-23-12:32:19.398 isengard [6420] lpr lp: Add_line_list: 'IF filter problems, error 'UNKN...', sep 'NULL', sort 0, uniq 0 2001-03-23-12:32:19.398 isengard [6420] lpr lp: cleanup: signal No signal, Errorcode -1, exits 1 . . . -- lpr debug report from script when run from commandline -- . . . 2001-03-23-12:31:23.605 isengard [6409] lpr lp: Write_outbuf_to_OF: read status 0, read 0, '' 2001-03-23-12:31:23.605 isengard [6409] lpr lp: Write_outbuf_to_OF: no more reading 2001-03-23-12:31:23.605 isengard [6409] lpr lp: Write_outbuf_to_OF: waiting 0 secs for pid 6411, suspend 0 2001-03-23-12:31:23.605 isengard [6409] lpr lp: Wait_for_pid: name 'IF', pid 6411, suspend 0, timeout 0 2001-03-23-12:31:23.605 isengard [6409] lpr lp: plp_waitpid: pid 6411, options 2 2001-03-23-12:31:23.606 isengard [6409] lpr lp: plp_waitpid: report 6411, status exit status 0 (JSUCC) 2001-03-23-12:31:23.606 isengard [6409] lpr lp: Wait_for_pid: pid 6411 exit status 'exit status 0 (JSUCC)' 2001-03-23-12:31:23.606 isengard [6409] lpr lp: Wait_for_pid: IF filter exited with status 0 2001-03-23-12:31:23.606 isengard [6409] lpr lp: Wait_for_pid: returning 'JSUCC', exit status 'exit status 0 (JSUCC)'
Re: can't print from acroread
peanut butter [EMAIL PROTECTED] writes: so the execution of the script is exactly the same, printing the exact same postscript file, while printing correctly from one execution (command line) yet not from the other (acroread). In cases where the same thing acts differently from different programs, I usually suspect the environment. Add env to your script, and see what differs. I don't know offhand what it could be, but it's worth a try. -- Alan Shutko [EMAIL PROTECTED] - In a variety of flavors! We read to say that we have read.
Re: can't print from acroread
In cases where the same thing acts differently from different programs, I usually suspect the environment. Add env to your script, and see what differs. I don't know offhand what it could be, but it's worth a try. -- Alan Shutko [EMAIL PROTECTED] - In a variety of flavors! We read to say that we have read. Great idea although nothing immediately jumps out at me as to what concerning the differences could cause the print failure. The differences were entirely environmental variables that were present in the environment coming from acroread yet absent in mine. Thus, I defined these extra environmental variables in my current shell environment and tried the same script from the command line. It still printed fine. Here's results of a diff between acroread's environment and mine, respectively: 2d1 ACRO_ARG0=/usr/bin/X11/acroread 4d2 LD_LIBRARY_PATH=/usr/lib/Acrobat4/Reader/intellinux/lib:/usr/lib/Acrobat4/Reader/intellinux/lib 10,11d7 XKEYSYMDB=/usr/lib/Acrobat4/Reader/intellinux/lib/XKeysymDB XFILESEARCHPATH=/usr/lib/Acrobat4/Reader/intellinux/%T/%L/%N%S:/usr/lib/Acrobat4/Reader/intellinux/%T/%l/%N%S:/usr/lib/Acrobat4/Reader/intellinux/%T/%N%S16d11 PSRESOURCEPATH=/home/py/psres:/home/py/fonts:/usr/psres:/usr/lib/Acrobat4/Reader/intellinux/fonts:/usr/lib/Acrobat4/Reader/../Resource/Encoding:/usr/lib/Acrobat4/Reader/../Resource/CMap:: 19c14 ACRO_INSTALL_DIR=/usr/lib/Acrobat4/Reader --- _=/usr/bin/env 25d19 ACRO_CONFIG=intellinux 28d21 _=/usr/bin/env Thanks for the suggestion, Paul -- Paul Yeatman (858) 534-9896[EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
Re: can't print from acroread
Not sure if this will help, but... I have the same symptom. I tried to print from acroread and nothing happened. I ended up shutting down after that. The next time I booted the system I discovered that I was unable to print from any application, and my cpu was pinned. I noticed that the process sucking most of the cpu was gs. After killing gs the cpu went to normal and printing resumed. Hope that's a hint. Cheers, Steve peanut butter wrote: Hi, I'm using lprng with filter /etc/magicfilter/ljet4-filter to an HP Laserjet 5M printer. Though things print fine from the command line, if I open a pdf with acroread, nothing prints when clicking the print button from within the application. A pop-up window will appear saying that the print job has been submitted and it will sequentially course through each page number of the document giving every sign that things should be printing yet nothing ever appears in the print queue, nothing ever comes out of the printer and an error message never shows up in any system log file (that I've ever checked, anyhow). Supposing this is too specific a problem for anyone to immediately have an idea as to the cause, can anyone at least suggest some manner at which to attempt to trace what's going on here and where the failure is occurring? Thanks. -- Paul Yeatman (858) 534-9896[EMAIL PROTECTED] == ==Proudly brought to you by Mutt== == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
can't print from acroread
Hi, I'm using lprng with filter /etc/magicfilter/ljet4-filter to an HP Laserjet 5M printer. Though things print fine from the command line, if I open a pdf with acroread, nothing prints when clicking the print button from within the application. A pop-up window will appear saying that the print job has been submitted and it will sequentially course through each page number of the document giving every sign that things should be printing yet nothing ever appears in the print queue, nothing ever comes out of the printer and an error message never shows up in any system log file (that I've ever checked, anyhow). Supposing this is too specific a problem for anyone to immediately have an idea as to the cause, can anyone at least suggest some manner at which to attempt to trace what's going on here and where the failure is occurring? Thanks. -- Paul Yeatman (858) 534-9896[EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
Re: can't print from acroread
have an idea as to the cause, can anyone at least suggest some manner at which to attempt to trace what's going on here and where the failure is occurring? What is the result if after trying to print you make an lpq, can you see your job in the queue? Regards Roberto Roberto Diaz [EMAIL PROTECTED] http://vivaldi.ddts.net Powered by ddt dynamic DNS Powered by GNU running on a Linux kernel. Powered by Debian (The real wonder) Concerto Grosso Op. 3/8 A minor Antonio Vivaldi (so... do you need beautiful words?)
Re: can't print from acroread
Supposing this is too specific a problem for anyone to immediately have an idea as to the cause, can anyone at least suggest some manner at which to attempt to trace what's going on here and where the failure is occurring? And.. what is your printer command you have selected in acroread? Regards Roberto Roberto Diaz [EMAIL PROTECTED] http://vivaldi.ddts.net Powered by ddt dynamic DNS Powered by GNU running on a Linux kernel. Powered by Debian (The real wonder) Concerto Grosso Op. 3/8 A minor Antonio Vivaldi (so... do you need beautiful words?)
Re: can't print from acroread
On Fri, Mar 16, 2001 at 11:18:00AM -0800, peanut butter wrote: Hi, I'm using lprng with filter /etc/magicfilter/ljet4-filter to an HP Laserjet 5M printer. Though things print fine from the command line, if I open a pdf with acroread, nothing prints when clicking the print button from within the application. A pop-up window will appear saying that the print job has been submitted and it will sequentially course through each page number of the document giving every sign that things should be printing yet nothing ever appears in the print queue, nothing ever comes out of the printer and an error message never shows up in any system log file (that I've ever checked, anyhow). Supposing this is too specific a problem for anyone to immediately have an idea as to the cause, can anyone at least suggest some manner at which to attempt to trace what's going on here and where the failure is occurring? can you print the file in question if you have acroread direct its output to a file, which you then send to the printer manually? Can you view the resulting PS-file in ghostscript? Erdmut -- Erdmut Pfeifer science+computing ag -- Bugs come in through open windows. Keep Windows shut! --
Re: can't print from acroread
* peanut butter [EMAIL PROTECTED], 20010316 21:08 +0100: Hi, I'm using lprng with filter /etc/magicfilter/ljet4-filter to an HP Laserjet 5M printer. Though things print fine from the command line, if I open a pdf with acroread, nothing prints when clicking the print button from within the application. Not sure if I can help you... Is lprng in the print dialog window's command line (/usr/bin/lpr here)? Did you try to specify a printer explicitely (-P)? Did you try to print to a file? Does it work from xpdf? Another wild guess, but why not: Try PS Level 1, specified in Acroread's prefs, or by piping through ps2ps -dLanguageLevel=1. Andre Berger[EMAIL PROTECTED]
Re: can't print from acroread
can you print the file in question if you have acroread direct its output to a file, which you then send to the printer manually? Can you view the resulting PS-file in ghostscript? Yes to both. Sorry not to mention this right off. I mentioned this the first time I attempted to post this message but apparently wasn't yet fully subscribed and neglected to save myself a copy. If I save the file as a postscript from the acroread print pop-up window, I can print the job without a problem from the command line and, thus, to no surprise, can also correctly display it with gv. Thus, the job seems to somehow never be making it outside acroread. In trying to diagnose the problem, I tried using another printer that I didn't realize hadn't been configured for the system by changing the printer command to /usr/bin/lpr -Plex. I received the same print error message I would have received from lprng if I had tried this from the command line yet it was displayed within a pop-up window from acroread. So obviously acroread is talking to lprng to some degree. -- Paul Yeatman (858) 534-9896[EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
Re: can't print from acroread
On Fri, 16 Mar 2001, peanut butter wrote: What is the result if after trying to print you make an lpq, can you see your job in the queue? Due to the problem, I discovered printop which graphically monitors printers and queues run by lprng. Nothing ever appears in the queue as far as I can tell. When the printer was busy printing another user's job, I started something from the command line just to ensure I could see something. Sure enough, one job waiting. Then tried the job again from with in acroread. The second job never appeared. And how do you print from a shell... are you using lpr or lpr -Pnameofprinter? And.. what is your printer command you have selected in acroread? In the printer command field is /usr/bin/lpr. It could be some problems with the name of your default queue? Regards Roberto Roberto Diaz [EMAIL PROTECTED] http://vivaldi.ddts.net Powered by ddt dynamic DNS Powered by GNU running on a Linux kernel. Powered by Debian (The real wonder) Concerto Grosso Op. 3/8 A minor Antonio Vivaldi (so... do you need beautiful words?)
Re: can't print from acroread
On Fri, Mar 16, 2001 at 11:18:00AM -0800, peanut butter wrote: Hi, I'm using lprng with filter /etc/magicfilter/ljet4-filter to an HP Laserjet 5M printer. Though things print fine from the command line, if I open a pdf with acroread, nothing prints when clicking the print button from within the application. A pop-up window will appear saying that the print job has been submitted and it will sequentially course through each page number of the document giving every sign that things should be printing yet nothing ever appears in the print queue, nothing ever comes out of the printer and an error message never shows up in any system log file (that I've ever checked, anyhow). Supposing this is too specific a problem for anyone to immediately have an idea as to the cause, can anyone at least suggest some manner at which to attempt to trace what's going on here and where the failure is occurring? Just a guess, but I had a similar problem with only certain .pdf documents. The error light on my Lexmark Optra E312 would flash when lpr was sending data to the printer and nothing was printed although there were no error messages. I used pdftops to convert the file to .ps and noticed that the first line said %!PS-Adobe-3.0. My printer only handles PS level 2, so I believe this was the problem. I think it had something to do with the way the document was created and neither acroread nor pdftops could convert to level 2 postscript, although I had selected level 2 in the acroread print dialog box. Bob
Re: can't print from acroread
Not sure if I can help you... Is lprng in the print dialog window's command line (/usr/bin/lpr here)? Did you try to specify a printer explicitely (-P)? Did you try to print to a file? Does it work from xpdf? Another wild guess, but why not: Try PS Level 1, specified in Acroread's prefs, or by piping through ps2ps -dLanguageLevel=1. Andre Berger[EMAIL PROTECTED] Hi, many of these questions are answered in responses to Roberto's and Erdmut's messages. Unfortunately, I failed to also post the list on my reponse to Roberto so if I can't rectify this soon, I'll address these questions, again. I tried your PS level 1 suggestion. It still would not print directly from acroread using this option. I don't know if this also satisfies your pipe to ps2ps suggestion. If not, I'm not quite understanding the suggestion. Thanks, again. Paul -- Paul Yeatman (858) 534-9896[EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
Re: can't print from acroread
On Fri, 16 Mar 2001, Roberto Diaz wrote: What is the result if after trying to print you make an lpq, can you see your job in the queue? Due to the problem, I discovered printop which graphically monitors printers and queues run by lprng. Nothing ever appears in the queue as far as I can tell. When the printer was busy printing another user's job, I started something from the command line just to ensure I could see something. Sure enough, one job waiting. Then tried the job again from with in acroread. The second job never appeared. And.. what is your printer command you have selected in acroread? In the printer command field is /usr/bin/lpr. -- Paul Yeatman (858) 534-9896[EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
Re: can't print from acroread
-In response to your message- --received from Bob Nielsen-- Just a guess, but I had a similar problem with only certain .pdf documents. The error light on my Lexmark Optra E312 would flash when lpr was sending data to the printer and nothing was printed although there were no error messages. I used pdftops to convert the file to .ps and noticed that the first line said %!PS-Adobe-3.0. My printer only handles PS level 2, so I believe this was the problem. I think it had something to do with the way the document was created and neither acroread nor pdftops could convert to level 2 postscript, although I had selected level 2 in the acroread print dialog box. Bob Well, I've saved the file to postscript using acroread and, alas, the first line also reads %!PS-Adobe-3.0 yet I can print it fine from the command line . . . things just won't print from acroread. Thus, it's not terribly impeding but I would be happy to solve the mystery and get the user who is complaining of this off my back. If it prints from the command line, I see no reason why it shouldn't print from acroread. -- Paul Yeatman (858) 534-9896[EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
Re: can't print from acroread
On Fri, Mar 16, 2001 at 01:01:31PM -0800, peanut butter wrote: can you print the file in question if you have acroread direct its output to a file, which you then send to the printer manually? Can you view the resulting PS-file in ghostscript? Yes to both. Sorry not to mention this right off. I mentioned this the first time I attempted to post this message but apparently wasn't yet fully subscribed and neglected to save myself a copy. If I save the file as a postscript from the acroread print pop-up window, I can print the job without a problem from the command line and, thus, to no surprise, can also correctly display it with gv. Thus, the job seems to somehow never be making it outside acroread. In trying to diagnose the problem, I tried using another printer that I didn't realize hadn't been configured for the system by changing the printer command to /usr/bin/lpr -Plex. I received the same print error message I would have received from lprng if I had tried this from the command line yet it was displayed within a pop-up window from acroread. So obviously acroread is talking to lprng to some degree. well, this is really a little strange... Perhaps you might want to try the following to get some more information: Write a shell script something like #!/bin/sh ls -l $1 /tmp/acroprint-debug.$$ cp $1 /tmp/acroprint-out.$$ /usr/bin/lpr -Pprinter $1 # substitute your printer here echo $? /tmp/acroprint-debug.$$ (the .$$ are not required, they just create a seperate pair of files for each try, with the PID appended) and run this instead of the /usr/bin/lpr from acroread's print dialogbox (e.g. Printer Command: /home/name/test-print -- no further options) This should (a) give you some info about the temp-file that acroread creates (- ls) (b) copy the temp-file to a safe place, before it gets deleted (- cp) (c) try to run the actual print command -- maybe it works from here (d) capture the return code of the print command -- should be 0 if OK Then you can also compare the /tmp/acroprint-out with the file you created when printing directly to a file from within the dialogbox. I guess both files should be identical. Also, feel free to add other debugging commands you could think of to the script... Don't know whether it helps ;) Erdmut -- Erdmut Pfeifer science+computing ag -- Bugs come in through open windows. Keep Windows shut! --
Re: can't print from acroread
On Fri, Mar 16, 2001 at 01:34:45PM -0800, Bob Nielsen wrote: I had a similar problem with only certain .pdf documents. The error light on my Lexmark Optra E312 would flash when lpr was sending data to the printer and nothing was printed although there were no error messages. I used pdftops to convert the file to .ps and noticed that the first line said %!PS-Adobe-3.0. My printer only handles PS just a short note: contrary to what one might think, the 3.0 in %!PS-Adobe-3.0 does not refer to the PostScript language level. Instead it states that the PS document adheres to the Adobe DSC (document structuring conventions) version 3.0 (with versioning independent from the PS level). The DSC mainly specify the syntax and sematics of the %%-comments. Erdmut level 2, so I believe this was the problem. I think it had something to do with the way the document was created and neither acroread nor pdftops could convert to level 2 postscript, although I had selected level 2 in the acroread print dialog box. -- Erdmut Pfeifer science+computing ag -- Bugs come in through open windows. Keep Windows shut! --
Re: can't print from acroread
Thanks for the clarification. Bob On Sat, Mar 17, 2001 at 01:16:17AM +0100, Erdmut Pfeifer wrote: On Fri, Mar 16, 2001 at 01:34:45PM -0800, Bob Nielsen wrote: I had a similar problem with only certain .pdf documents. The error light on my Lexmark Optra E312 would flash when lpr was sending data to the printer and nothing was printed although there were no error messages. I used pdftops to convert the file to .ps and noticed that the first line said %!PS-Adobe-3.0. My printer only handles PS just a short note: contrary to what one might think, the 3.0 in %!PS-Adobe-3.0 does not refer to the PostScript language level. Instead it states that the PS document adheres to the Adobe DSC (document structuring conventions) version 3.0 (with versioning independent from the PS level). The DSC mainly specify the syntax and sematics of the %%-comments. Erdmut level 2, so I believe this was the problem. I think it had something to do with the way the document was created and neither acroread nor pdftops could convert to level 2 postscript, although I had selected level 2 in the acroread print dialog box.
