| Andreas Klemm on Sun, 5 Nov 2000 09:16:36 +0100 (CET) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| [cliffy@cliffhangers.screaming.net: Printing in Linux] |
Forwarded to the official apsfilter help channel. -- Andreas Klemm Powered by FreeBSD SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html My homepage................................ http://people.FreeBSD.ORG/~andreas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/
- To: andreas@xxxxxxxxxxxxx
- Subject: Printing in Linux
- From: "C.D.McDiarmid" <cliffy@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 Oct 2000 19:07:04 +0000
- Organization: Dog Wardens
Please look over attached file and see if you can help. Setting up a printer on Linux is driving me to distraction. MAC(UK) # $ApsCVS: src/apsfilter/HOWTO-BUGREPORTS,v 1.12 2000/04/30 14:51:48 andreas Exp $ please mail this form to: andreas@klemm.gtn.com with the subject: Nothing happens through apsfilter. cat print.txt > /dev/lp0 prints text, albeit stepped. echo hello...etc prints page. (1) Some simple questions: Operating System : if Linux : Built from scatch apsfilter Rel. : apsfilter-5.4.2 ghostscript Rel. : gs 6.01 (make sure with gs -h) Printer : DJ 500C serial/parallel : parallel printer Mono/Color : mono printer Postscript-Printer: no Print Resolution : 300 X 300 or : GS_RESOL set by apsfilterrc file ? or : set by filterscript name ? Your Full Name : Cliff Mcdiarmid Your e-mail addr : cliffy@cliffhangers.screaming.net (2) - Problem description - what ghostscript printer driver did you use ? djet500 (3) Any error messages from your operating system, indicating trouble concerning TCP/IP, lpd ? Browse your systems syslog logfiles, i.e. /var/log/messages or /var/log/lpd-errs, ... ? Oct 27 18:31:18 cliffhangers lpd[17550]: can't find user - can't fork Oct 27 18:31:18 cliffhangers lpd[17550]: lp: filter 'f' terminated (termsig=88) Oct 27 18:31:18 cliffhangers lpd[17550]: lp: job could not be printed (cfA000cliffhangers) (4) Did you read all help-files ? The most important are: - INSTALL, FAQ, README, KNOWN_BUGS,TODO, ChangeLog - HOWTO-BUGREPORTS, doc/README.TeX, doc/REMOTE-PRINTING, - doc/TROUBLESHOOTING If not, then please do so first. YES (5) Did you enable debugging in the apsfilter shellscript to track down simple errors yourself ? More infos on how to do this, see doc/TROUBLESHOOTING, section 1.5. Please do so first !!! If you can't find the problem, then please send me the debugging output of *exactly* one print session. Yes, but no output was present in log file (6) The printer entry from your /etc/printcap file, that caused trouble, i.e. if you have trouble forcing ASCII printing the entry from the printer named auto would be fine: # LABEL apsfilter # apsfilter setup Sun Apr 23 13:08:51 CEST 2000 # # DON'T DELETE THIS: # APS_BASEDIR:/usr/local/apsfilter # # APS1_BEGIN:printer1:stcolor:a4:default # - don't delete start label for apsfilter printer1 # - no other printer defines between BEGIN and END LABEL # lp|aps1-stcolor-a4-auto-default|Printer1 stcolor a4 auto default:\ :lp=/dev/lpt0:\ :sd=/var/spool/lpd/printer1-stcolor-a4-auto-default:\ :lf=/var/spool/lpd/printer1-stcolor-a4-auto-default/log:\ :af=/var/spool/lpd/printer1-stcolor-a4-auto-default/acct:\ :if=/usr/local/apsfilter/filter/aps1-stcolor-a4-auto-default:\ :mx#0:\ :sh: (7) Did you modify /etc/apsfilterrc or /etc/apsfilterrc.<GS_DRIVERNAME> ? NO If you modified the file, try printing without the modifications. Still problems ? (8) Do you have a private and modified copy of /etc/apsfilterrc in NO your login/home directory ($HOME/.apsfilterrc or $HOME.apsfilterrc.<GS_DRIVERNAME> ? (9) Do you use an (old) global /etc/apsfilterrc file ? NO Apsfilter 5.1.5 an newer should have printer specific settings only in /etc/apsfilterrc.<gs-drivername> /etc/apsfilterrc is global for all printers, so you should avoid printer specific settings. Best is to backup and remove the file when doing a new installation. (10) Is it perhaps a file type recognition problem ? NO The output of your file(1) command on the file that can't be printed: i.e. type: file file_that_can't_be_printed README: English text (11) The part of your printers logfile, that logged the commands of Nothing present your failed print session, see lf= in /etc/printcap, i.e.: lp|aps1-stcolor-a4-auto-default|Printer1 stcolor a4 auto default:\ :lf=/var/spool/lpd/printer1-stcolor-a4-auto-default/log:\ :af=/var/spool/lpd/printer1-stcolor-a4-auto-default/acct:\ So you find debugging output in the file /var/spool/lpd/printer1-stcolor-a4-auto-default/log This logfile contains debugging data, if you enabled debugging as described in TROUBLESHOOTING, section 1.5. (12) Mostly true on Linux Distributions: Do you use the traditional printer spooler (lpd) or the one that is called LPRng (line printer next generation) ? Thanks for complete informations ! Andreas ///