Bug 1803 - Printtool not compatible with ghostscript 5.50
Printtool not compatible with ghostscript 5.50
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: printtool (Show other bugs)
5.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-03-25 19:36 EST by nstn1291
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-03-27 18:55:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description nstn1291 1999-03-25 19:36:44 EST
I have to use HylaFAX to send facsimile messages.
I downloaded the HylaFAX RPM from their Web page.
It insisted that I use ghostscript 5.10 or later.
I downloaded ghostscript 5.50 from its home page.
I am using a HP LaserJet IIIP printer.
The driver that ghostscript 5.50 has for this device is
not named the same as the Printtool drivers.
  /var/spool/lpd/lp1/filter
  /var/spool/lpd/lp1/asc-to-ps.fpi
  /usr/lib/rhs/rhs-print-filters/asc-to-ps.fpi
all needed manual changes to get the printer working again.

Suggestion:  have printtool get its print driver names for
the user to select from the "gs -h" output so it will always
match what is actually available.
Comment 1 Bill Nottingham 1999-03-26 10:39:59 EST
Unfortunately, printtool needs more than just the driver
names; it needs the options it supports, etc. What
driver that's in 5.5 are you trying to use?
Comment 2 Bill Nottingham 1999-03-27 18:55:59 EST
ghostscript-5.5 comes with the ljet3d driver, at least AFAICT
from reading the source, so that shouldn't be a problem.

In any case, printtool does check the output of gs -h when
setting up the printer; however, we can't check if you
configure the printer and *then* change ghostscript.

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