Bug 57915

Summary: /usr/local PATH issue
Product: [Retired] Red Hat Linux Reporter: rdt
Component: foomaticAssignee: Tim Waugh <twaugh>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-01-30 14:30:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
output of printconf-tui --Xexport
none
status.lp none

Description rdt 2002-01-01 13:57:46 UTC
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

Using foomatic-1.1-0.20011103.1

How reproducible:
Always

Steps to Reproduce:
1. lpr anything
2.
3.
	

Actual Results:  nothing

Expected Results:  printing

Additional info:

Comment 1 rdt 2002-01-01 14:00:31 UTC
Created attachment 41573 [details]
output of printconf-tui --Xexport

Comment 2 rdt 2002-01-01 14:02:42 UTC
Created attachment 41574 [details]
status.lp

Comment 3 rdt 2002-01-04 01:46:39 UTC
 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.


which gs

gave /usr/bin/gs and 

gs --version

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.


Comment 4 Tim Waugh 2002-01-24 16:42:52 UTC
Okay, this seems to come from lpdomatic, which is part of the foomatic package.


Comment 5 Tim Waugh 2002-01-30 13:45:18 UTC
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..


Comment 6 rdt 2002-01-30 14:30:16 UTC
> Arguably this is the correct behaviour: /usr/local is where package
overrides    can go.

The default PATH would appear to be

/bin:/usr/bin:/usr/local/bin:/usr/bin/X11:/usr/X11R6/bin

so /usr/bin/ overrides /usr/local/bin/

Comment 7 Tim Waugh 2002-01-31 14:21:38 UTC
Fixed in foomatic-1.1-0.20020130.1.