Bug 71934

Summary: Apsfilter (or lpr) operates erratically
Product: Ports & Packages Reporter: Rob Lytle <europax>
Component: Individual Port(s)Assignee: andreas <andreas>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Rob Lytle 2004-09-20 13:40:29 UTC 
      Apsfilter requires usually two invocations in order to print a document.  Unfortunately, since I installed Apsfilter first, I cannot tell whether this is a problem with lpr itself.  I may have to wipe the apsfilter portion of printcap clean in order to test this.

Fix: 

none
How-To-Repeat:       Compile apsfilter from ports.  Go through the setup utility.  In my case the driver was generic postscript, 600dpi, /dev/lpt0, parallel port,  and some minor params I have forgotten.
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2004-12-17 23:27:32 UTC 
Responsible Changed
From-To: freebsd-bugs->andreas

Over to maintainer
Comment 2 andreas freebsd_committer freebsd_triage 2005-01-30 12:22:44 UTC 
On Fri, Dec 17, 2004 at 11:28:12PM +0000, Tilman Linneweh wrote:
> Synopsis: Apsfilter (or lpr) operates erratically
> 
> Responsible-Changed-From-To: freebsd-bugs->andreas
> Responsible-Changed-By: arved
> Responsible-Changed-When: Fri Dec 17 23:27:32 GMT 2004
> Responsible-Changed-Why: 
> Over to maintainer
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=71934

Not reproduceable here, but I don't have a parallel port to test.
I print via remote printer (printer on USB port of DSL router).

>From what I see you are using a BETA version of FreeBSD 5.3.

If all further troubleshooting fails - see below - I would suggest
as strategy to upgrade to 5.3-STABLE via cvsup and do the usual
make buildworld/installworld + new kernel after reading src/UPDATING.
Updating with mergemaster should be done as well.

With the few informations provided nobody can tell, where
something fails on your system.

What could be done is to break the printing process into several steps
that might give an idea where something fails.

1. use aps2file to let apsfilter run and print the result to 
   stdout (into a file).
   i.e.: aps2file file_2_print > printresult

See apsfilter handbook:
http://www.apsfilter.org/docs/apsfilter-handbook-current.html#usage_file

2. cat printresult > /dev/You_Print_Device

If apsfilter fails at 1 you could try apsfilter debugging
See handbook:
http://www.apsfilter.org/docs/apsfilter-handbook-current.html#help_you_bug


Good luck

	Andreas ///

-- 
Andreas Klemm - Powered by FreeBSD 5.1-CURRENT
Need a magic printfilter today ? -> http://www.apsfilter.org/
Comment 3 andreas freebsd_committer freebsd_triage 2005-01-30 12:23:32 UTC 
State Changed
From-To: open->feedback

waiting for feedback on suggested actions
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2005-08-06 20:44:43 UTC 
State Changed
From-To: feedback->closed

Feedback timeout (> 6 months).