Yast messes up /etc/printcap the first time it tries to add a printer. I think local printers are configured using apsfilter (called by YaST.) Here is a sample of what you get for an HP postscript printer: ### BEGIN apsfilter: ### PS_300dpi letter mono 300 ### # Warning: Configured for apsfilter, do not edit the labels! # apsfilter setup Fri Sep 24 14:52:43 CDT 1999 # ascii|lp1|PS_300dpi-letter-ascii-mono-300|PS_300dpi letter ascii mono 300:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300:\ :lf=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/log:\ :af=/var/spool/lpd/PS_300dpi-letter-ascii-mono-300/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-ascii-mono-300:\ :la@:mx#0:\ :tr=:cl:sh:sf: # lp|lp2|PS_300dpi-letter-auto-mono-300|PS_300dpi letter auto mono 300:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-auto-mono-300:\ :lf=/var/spool/lpd/PS_300dpi-letter-auto-mono-300/log:\ :af=/var/spool/lpd/PS_300dpi-letter-auto-mono-300/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-auto-mono-300:\ :la@:mx#0:\ :tr=:cl:sh:sf: # raw|lp3|PS_300dpi-letter-raw|PS_300dpi letter raw:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/PS_300dpi-letter-raw:\ :lf=/var/spool/lpd/PS_300dpi-letter-raw/log:\ :af=/var/spool/lpd/PS_300dpi-letter-raw/acct:\ :if=/var/lib/apsfilter/bin/PS_300dpi-letter-raw:\ :la@:mx#0:\ :tr=:cl:sh:sf: # ### END apsfilter: ### PS_300dpi letter mono 300 ### Check /etc/printcap after you configure the printer. There should not be any empty line in the file, the printer daemon chokes when that happens, at least in earlier versions of suse. As root you can clean the queue with: # lpc clean all (or "lpc clear all", I don't remember) # lpc restart all Good luck. -- Rafael Herrera -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/