From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.3-12 i586)

Description of problem:
The undesired behavior we are seeing is a blank page following printing of
a text file on a remote print queue.

We have an HP LaserJet 4000 attached to the parallel port of a Linux 7.1
server.  The server's printcap entry for the queue is as follows.
ps817|lp:\
        :sh:\
        :ml=0:\
        :mx=0:\
        :sd=/var/spool/lpd/ps817:\
        :lp=/dev/lp0:\
        :lpd_bounce=true:\
        :if=/usr/share/printconf/mf_wrapper:
This was created using printconf-gui with no unusual options, and the EOT
box was not checked.  It works fine as a local printer for both text and
PostScript.
When printconf-gui is used to create printcap on clients, entries for this
remote queue are as follows:
ps817|lp:\
        :sh:\
        :ml=0:\
        :mx=0:\
        :sd=/var/spool/lpd/ps817:\
        :rm=pascal:\
        :rp=ps817:\
        :lpd_bounce=true:\
        :if=/usr/share/printconf/mf_wrapper:
Again, this was done with no special options and EOT not checked.  The
behavior is that text files printed from the client to this remote queue
have a blank trailer page.  PostScript does not have this problem.
The printcap(5) manpage, in the section on Bounce Queues, says ``This
[setting lpd_bounce flag] should only be done in server printcap
entries''.  There may also be a bug in lpr or lpd, since lpr_bounce and
lpd_bounce both seem to be ignored.  In fact, the only way we have found to
prevent the blank trailer pages is to remove the if option in the client
printcap entries.  But I'm not sure I have fully understood this section of
the man page.  If lpr and lpd are in fact behaving correctly, then
printconf-gui evidently should also not set if for remote queues.
I suppose it is also possible that the bug is in magicfilter, when used to
send output to a remote queue.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Set up a local queue using printconf-gui.  Take the default options.
2. On a remote machine, set up a remote queue to the queue defined in step
1.   Take the default options.
3. On the remote machine, print a text test page.  On the print server,
print a text test page.
	

Actual Results:  On remote machine, text test page is followed by a blank
page.  On print server, it is not.

Expected Results:  Both machines should have printed the test page only,
with no following blank page.

Additional info:

We have worked around this by manually editing printcap files, but we would
like to be able to use printconf-gui.