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 6377 - lpr does not work with WP 8.0
lpr does not work with WP 8.0
Product: Red Hat Linux
Classification: Retired
Component: lpr (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Depends On:
  Show dependency treegraph
Reported: 1999-10-26 04:22 EDT by miked
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-11-22 12:54:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description miked 1999-10-26 04:22:39 EDT
lpr does not work with WordPerfect 8.0
Comment 1 Bill Nottingham 1999-10-26 10:48:59 EDT
Can you give some more details?

How does it fail?

What version of lpr are you using?
Comment 2 Bill Nottingham 1999-10-26 17:48:59 EDT
OK; how does it fail?  How is it being invoked, and what printers
do you have set up?
Comment 3 Bill Nottingham 1999-10-26 17:49:59 EDT
Also, does it work with other applications?
Comment 4 Bill Nottingham 1999-10-27 12:01:59 EDT
WordPerfect uses its own printer drivers; hmm, that
could be a problem. Does WordPerfect still actually
use lpr, or does it write derectly to the port?
Comment 5 Bill Nottingham 1999-10-27 15:14:59 EDT
Yes, that sounds like it's trying to convert WordPerfect's
output to whatever the printer supports.

Hmm... not sure how to handle this; lpr doesn't expect
native data.
Comment 6 Bill Nottingham 1999-11-01 12:09:59 EST
One thing you could do is set up a different printer entry
in /etc/printcap that uses the same device, but doesn't use
an input filter (no if=<whatever> entry). That should work
OK, if WP is doing its own filtering/conversion.
Comment 7 Bernhard Rosenkraenzer 2000-07-17 11:15:18 EDT
If this is lpr related at all (we don't have access to WP source, so we can't be
sure what it's doing), it should be fixed in rawhide by the move to LPRng.

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