Red Hat Bugzilla – Bug 84167
PATH set wrong when VNC started from init.d
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461)
Description of problem:
PATH for user "whooper" when logged in via SSH:
PATH for user "whooper" under an xterm in VNC (started from /sbin/service
This cause problems when trying to run apps that normally use consolehelper
(up2date, setup, redhat-config-*) because the directory order is wrong.
Also present in the Phoebe2 beta. Not sure about RH 8.0, but I assume it is
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start VNCserver (/sbin/service vncserver start)
2. Open a term
3. Look at environment (printenv)
Actual Results: PATH with /sbin in front of /bin, etc.
Expected Results: Same PATH as other logins (console, ssh, telnet, etc.)
Adding the "-l" option to the su line in the /etc/init.d/vncserver script makes
Which is probably "close enough".
Still exists in FC1. Should I file a seperate bug for it?
Should be fixed in 4.0-9: I added '-l' to the runuser call as you suggested.
Although I don't think this needs an update for FC3, I've made the change in CVS
for any future updates that might be made for vnc in FC3.
Please confirm that it fixes it for you. It will be in Fedora development tomorrow.
Yep, that did the trick. Thanks.
Would be nice if this was in the fc3 updates since it bit me. Had to manually
add the -l before the -c in the first runuser to get correct PATH in xterms
automatically. (Note to readers: fc3 apparently no longer uses su but runuser as