Red Hat Bugzilla – Bug 57915
/usr/local PATH issue
Last modified: 2007-04-18 12:38:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i586)
Description of problem:
Using the ljet4 driver fails to send anything to the printer. Yet pcl
sent raw to the printer and cat ... > /dev/lp0 both work.
Version-Release number of selected component (if applicable):0.3.52-1
Steps to Reproduce:
1. lpr anything
Actual Results: nothing
Expected Results: printing
Created attachment 41573 [details]
output of printconf-tui --Xexport
Created attachment 41574 [details]
it seems to have been an old not-uninstalled binary of gs-7.01 in
/usr/local/bin that was causing my problem. What isn't clear is why it was
It seems to have been an old not-uninstalled binary of gs-7.01 (which
was seriously broken) in /usr/local/bin that was causing my problem.
What isn't clear is why it was being used.
gave /usr/bin/gs and
gave gs-6.51 (or 7.03). But 7.01 was mentioned in status.lp; I would guess
there is a faulty path in one of the scripts.
Okay, this seems to come from lpdomatic, which is part of the foomatic package.
Arguably this is the correct behaviour: /usr/local is where package overrides can go.
But I think in this context it's not really all that appropriate. Fixing..
> Arguably this is the correct behaviour: /usr/local is where package
overrides can go.
The default PATH would appear to be
so /usr/bin/ overrides /usr/local/bin/
Fixed in foomatic-1.1-0.20020130.1.