Bug 62058 - Environment variables in /etc/profile not loaded
Summary: Environment variables in /etc/profile not loaded
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: bash
Version: skipjack-beta1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: wdovlrrw
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-27 04:19 UTC by Gil Chilton
Modified: 2007-04-18 16:41 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-04-01 04:28:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Gil Chilton 2002-03-27 04:19:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
After upgrading a 7.2 install, the previously defined environment variables 
in /etc/profile no longer are loaded into the environment.  I can even manually 
execute the script after changing the permissions to execute and the parameters 
still do not load.  I have to cat the file to the monitor and copy and paste 
the export statements to the command line for them to work.  If copy only the 
relevant portions of /etc/profile into a separate file, the same issue remains.

The first time I started up skipjack, I logged in as root, noticed that the 
variables were not loaded, logged out, logged in as a non-root account, still 
did not see the variables, logged out, and logged in as root and suddenly saw 
the variables loaded.  I have not been able to repeat this sequence since.

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1. Login and look for environment variables in /etc/profile
2. Variables are not setup
3.
	

Actual Results:  No changes defined in /etc/profile or moved to a different 
script are loaded into the environment.

Expected Results:  Environment variables exported in /etc/profile should be 
loaded during login process.

Additional info:

Comment 1 Bill Nottingham 2002-03-27 19:51:28 UTC
How are you logging in?

Comment 2 Gil Chilton 2002-03-28 14:32:07 UTC
KDE

Comment 3 Gil Chilton 2002-03-28 14:33:11 UTC
The problem occurs with KDE but not when I bypass X (Ctrl-Alt-F2) and login 
directly to the machine.

Comment 4 Gil Chilton 2002-04-01 04:28:12 UTC
This item appears to be corrected with the updates available via up2date on 
3/29/02.

Comment 5 Bernhard Rosenkraenzer 2002-04-01 09:15:45 UTC
Yes, this was caused by bad kdm settings.


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