Subject: Bug#1382: Issue resolved

From: Fred Chen <[email-masked]>
Date: Wed, 17 Apr 2019 01:44:29 -0700

It turns out the source of the problem was a single line in the LDAP user’s .bashrc that was not in the local user’s config.

I originally did not even look at this because both the local user and the LDAP user were configured with /bin/csh as their login shell but it seems that the .bashrc is still read by the desktop manager or some other service as part of the Xsession.

We were using environment modules and the offending line was calling “module load” on a module that then loaded other modules.

When a new bash shell is started from the user’s session, there doesn’t seem to be a problem so I’m not sure why this terminates the session but it’s mostly a non-issue now for us.