Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 21825 - Error when initialising bash in a terminal window
Error when initialising bash in a terminal window
Product: Red Hat Linux
Classification: Retired
Component: bash (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2000-12-06 15:52 EST by alan.hughes4
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-12-06 15:52:46 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 alan.hughes4 2000-12-06 15:52:43 EST
On a vanilla install of RH 7.0, when starting bash in a KDE terminal 
window the following message appears:

    Bad : modifier in $ (/)

Not all environment variables are set up after this has occured.

Starting bash again *does not* result in the error message, and all 
environment variables are correctly set. I therefore conclude that this is 
a situation associated with the special case of bash running the 
initialisation scripts without environment variables having been set up.

I have checked all the scripts that appear to be run, and nothing stands 
out as being obviously wrong. Therefore I'd like to toss this in your lap.

Similar behaviour has been observed when starting tcsh under identical 
conditions. This behaviour was not observed under previous RH releases.
Comment 1 Bernhard Rosenkraenzer 2000-12-12 12:04:45 EST
I can't reproduce this; it's probably caused by customized startup scripts.
Comment 2 alan.hughes4 2000-12-12 13:22:04 EST
As stated in the original bug report, this is a *vanilla* install of RH 7.0 (to 
be specific Delux Edition boxed set - not a downloaded version). No 
customisations had been performed when the problem was first identified. Since 
then I've attempted to locate the faulty script, but have not had any luck so 

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