Description of problem:
The environment variable PATH has no /usr/local/bin (but has two
[zaitcev@niphredil ~]$ echo $PATH
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log in into GNOME
2. Launch gnome-terminal
3. Run echo $PATH
I don't really know what broke, because I did not update Rawhide for
a month due to X issues. The setup RPM was updated, but it seems
benign. Ditto initscripts. So, I think maybe gdm, because gdm
Note that logging in on text console, everything is ok.
Are you still seeing this with current rawhide?
Re-checked now, still the same (gdm-2.21.9-3.fc9).
so gdm run exactly one login shell as part of the login process. The login
shell will source /etc/profile and ~/.bash_profile
~/.bash_profile by default sources ~/.bashrc
are you frobbing PATH in ~/.bash_profile or ~/.bashrc ?
(In reply to comment #3)
> are you frobbing PATH in ~/.bash_profile or ~/.bashrc ?
Of course not, jeez! I wouldn't bother you if this was something
like that. But I checked just in case right now, and nope.
I rechecked /etc/profile and /etc/profile.d/* too.
Look, the problem is two fold:
1) I didn't do anything, just ran "yum update" one day and it started.
2) I have no clue what component is actually at fault, but everything
works as before on Linux console. So I'm using gdm as kind of a
bracket for "things which parent my processes in GNOME session".
Maybe it's the gnome-session, not gdm. How do I find out?
Unfortunately, gnome-terminal daemonizes itself or else its parent
has exited, so I cannot follow the process tree to the offender.
So this is totally gdm's fault:
Will be fixing shortly.
Should be fixed in gdm-2.21.10-0.2008.03.18.2.fc9 which won't make the beta.
Seems to be fixed in rawhide.
I don't think this is the correct fix.
gdm is setting the PATH since there is no path set at all.
The PATH should have been caried through from the users login shell, but
something is wiping it out.
gdm runs before login, the users login shell runs after login.