Bug 55748

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.16-22 i686)

Description of problem:
I've been an avid linux user now for many years. I've been using a LaserJet
6L printer attached to a linux file server for the last 3 years without a
problem, first on RHL 5.2, then on 7.0. Well, I just rebuilt my server with
RHL7.2 and can no longer print. I'm using printconf-tui to generate the
printer config (X? on a server? dont be silly...) and it seems to generate
/etc/printcap fine. Firing off a test page (ASCII and Postscript) from
within printconf-tui fails, and printing from the command line with the
usual tools (lp/lpr) also does not work. However, I know the hardware is
all working properly; using cat FILENAME > /dev/lp0  spits FILENAME out the
printer.

I'll walk through the process of creating the printer and then firing off
the test pages to help reproduce the environment and situation. This will
start from having no printer configured at all.

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


How reproducible:
Always

Steps to Reproduce:
1. Launch printconf-tui.
2. Choose new.
3. Select a queue name. I use lpd, but what's in a name?
4. Leave Local Printer Device selected, and tab down to Next.
5. /dev/lp0 is highlighted. Tab down to next.
6. Under HP, select LaserJet 6L, and select the ljet4 driver. Tab and
select next.
7. Select Finish.
8. Tab over to the Test button.
9. Saving is a good thing. Choose Yes.
10. Arrow down to ASCII text testpage, then hit tab and choose test.
11. Sent ASCII test page to "lpd". Hit OK.
12. Hit enter to choose Test again.
13. US Letter Postscript Testpage is automatically highlighted. Hit tab to
choose test.
14. Sent US Letter PostScript Testpage to "lpd". Hit OK.
15. Tab and choose Exit to end printconf-tui.

	

Actual Results:  Nothing. The printer wakes up (bottom light comes on) but
nothing ever comes out.

Expected Results:  Test pages!


Additional info:

I'll attach the resulting files:
/etc/printcap
/var/spool/lpd/lpd/status.lpd

and the output of rpm -qa. Please note that I'm running all the latest
updates from RedHat. I've tried rolling back the updates (removing the 2
Omni packages, rolling back ghostscript and printconf to stock RH7.2) but
that wasnt successful either; it produced a different set of errors.