Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 67503 - cannot print postscript
cannot print postscript
Product: Red Hat Linux
Classification: Retired
Component: LPRng (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-06-26 10:18 EDT by Jeff Stern
Modified: 2007-04-18 12:43 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-16 12:00:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
zip of my /var/spool/lpd/lp0 directory (15.20 KB, application/zip)
2002-06-26 10:21 EDT, Jeff Stern
no flags Details

  None (edit)
Description Jeff Stern 2002-06-26 10:18:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Description of problem:
i upgraded to rh7.3 and now i cannot print out anything other than plain text.

my setup:

my printer is an epson stylus color 900 sitting on a windows xp box on a machine
on the same subnet. the printer works fine for the xp box. i am using the
gimp-print driver.

it also used to print out bitmaps and other documents requiring ghostscript
rendering. but after i upgraded to 7.3, it didn't do anything: just showed job
in lpq, as 'done' but that's it. no printout.

i removed the printer entry in printconf-gui and re-installed with same
parameters, and it works *slightly* better: now the printer on the remote xp box
*does* start, but what it does is chunk out tons of blank pieces of paper (for
the Test Letter Postscript page in printconf-gui). it does, however, print out a
test ASCII text page for the linux box, from printconf-gui, perfectly fine, *if*
i de-select the default option of 'render text as postscript' in the Driver
Options tab.

i have tried the omni-print driver, as well, and it sends a bunch of blank pages
out the printer, too, *although* one of them does have a *piece* of the
printout, but it is a bit warbled.

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

How reproducible:

Steps to Reproduce:
1. explained above
2. explained above
3. explained above

Additional info:
Comment 1 Jeff Stern 2002-06-26 10:21:01 EDT
Created attachment 62727 [details]
zip of my /var/spool/lpd/lp0 directory
Comment 2 Jeff Stern 2002-06-26 10:22:37 EDT
also, the print jobs seem to 'hang around' in the lp queue.. here is a printout
of lpq:
[root@vp184136 root]# lpq
Printer: lp0@vp184136
 Queue: no printable jobs in queue
 Server: no server active
 Status: job 'root@vp184136+184' saved at 07:02:35.436
 Rank   Owner/ID                  Class Job Files                 Size Time
done   root@vp184136+155            A   155 it                     123 07:01:26
done   root@vp184136+184            A   184 it                     123 07:02:35
[root@vp184136 root]#
Comment 3 Need Real Name 2002-06-27 13:47:35 EDT
I'm having the same problem after upgrading from 7.0 to 7.3.  I can print test
pages from the printtool, but lp/lpr do nothing even though lpq suggests that
the job has been completed.
Comment 4 kirk.erickson 2002-07-12 15:53:03 EDT
I'm experiencing a similiar failure with an HP855Cse after scratch installing 7.3.
I had no problems under 7.2, apparently using the cdj850 driver.  Now, I see jibberish at
the top of a page and then many blank pages generated.  This happens when I attempt
using printtool test too.

The gimp driver is silent for me too...
Comment 5 Tim Waugh 2003-01-20 13:49:40 EST
(Moving to the correct component.)
Comment 6 Tim Waugh 2003-01-20 13:51:28 EST
If you reconfigure the queue (remove it and add in again), does that make the
problem go away?  That driver changed name.
Comment 7 Tim Waugh 2005-09-16 12:00:50 EDT
We no longer ship LPRng.

Note You need to log in before you can comment on or make changes to this bug.