From nobody@FreeBSD.org  Mon Sep 20 12:37:15 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 580BC16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 20 Sep 2004 12:37:15 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4FF1343D5C
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 20 Sep 2004 12:37:15 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i8KCbF77045804
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 20 Sep 2004 12:37:15 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i8KCbFgk045803;
	Mon, 20 Sep 2004 12:37:15 GMT
	(envelope-from nobody)
Message-Id: <200409201237.i8KCbFgk045803@www.freebsd.org>
Date: Mon, 20 Sep 2004 12:37:15 GMT
From: Rob Lytle <europax@comcast.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Apsfilter (or lpr) operates erratically
X-Send-Pr-Version: www-2.3

>Number:         71934
>Category:       ports
>Synopsis:       Apsfilter (or lpr) operates erratically
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    andreas
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 20 12:40:29 GMT 2004
>Closed-Date:    Sat Aug 06 19:46:33 GMT 2005
>Last-Modified:  Sat Aug 06 19:46:33 GMT 2005
>Originator:     Rob Lytle
>Release:        RELENGE_5
>Organization:
none
>Environment:
FreeBSD lm741n.dyndns.org 5.3-BETA5 FreeBSD 5.3-BETA5 #0: Sun Sep 19 03:04:23 PDT 2004     rob@lm741n.dyndns.org:/usr/obj/usr/src/sys/ROBKERN  i386
    
>Description:
      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.
>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.
>Fix:
      none
>Release-Note:
>Audit-Trail:
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 
State-Changed-From-To: open->feedback 
State-Changed-By: andreas 
State-Changed-When: Sun Jan 30 12:23:32 GMT 2005 
State-Changed-Why:  
waiting for feedback on suggested actions 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71934 

From: Andreas Klemm <andreas@freebsd.org>
To: Tilman Linneweh <arved@freebsd.org>
Cc: freebsd-bugs@freebsd.org
Subject: Re: ports/71934: Apsfilter (or lpr) operates erratically
Date: Sun, 30 Jan 2005 13:22:44 +0100

 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/
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Sat Aug 6 19:44:43 GMT 2005 
State-Changed-Why:  
Feedback timeout (> 6 months). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71934 
>Unformatted:
