RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If user's login shell is tcsh and the user set PATH
into .cshrc or .tcshrc, then the user see the PATH twice
in Gnome-terminal or xterm

Version-Release number of selected component (if applicable):
RHEL6.3
gnome-desktop-2.28.2-9.el6.x86_64
gnome-terminal-2.31.3-7.el6.x86_64
tcsh-6.17-19.el6_2.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL6.3. Install tcsh.
2. Create a user.
3. Set the user's login shell as tcsh.
4. Set the path into ~/.cshrc.
setenv PATH ${PATH}:/home/iida1/bin

5. Login to GNOME.
6. Open gnome-terminal or xterm.
7. env |grep PATH

Actual results:
PATH=/usr/local/bin:/usr/bin:/bin:/home/iida1/bin:/home/iida1/bin

Expected result:
PATH=/usr/local/bin:/usr/bin:/bin:/home/iida1/bin

Additional info:
Login from ssh, and env |grep PATH, it display expected result.
The symptom is reproduced with gnome-terminal and xterm.
The symptom reproduced with .cshrc and .tcshrc.

Business impact: Low

i think this is probably by design.   When you log in, a login shell gets run.  When you start a terminal, an interactive shell gets started. In both cases, I believe .cshrc will get sourced.

you can put:

switch(":${PATH}:")
    case "*:/home/iida1/bin:*":
    breaksw
    default:
    ...set path here ...
endsw

to filter the dupes i believe.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.