...
We kindly ask that you please terminate any sessions that you no longer need as they do use resources.
| Anchor | ||||
|---|---|---|---|---|
|
When connecting to Argon with FastX version 2 to open a Desktop graphical desktop session such as MATE sessionor KDE, sometime you might get an error saying "cannot connect to the bus like 'The command "mate-session" exited'. This happens particularly can occur if you have installed Anaconda to work with Jupyter on the cluster. Anaconda changes the .bashrc file with the PATH settings and causes the wrong dbus programs to be used. There is a fix available for this particular problem.
Change your PATH variable in .bashrc FROM:
export PATH="/Users/YOURHAWKID/anaconda2/bin:$PATH”
TO:
export PATH="$PATH:/Users/YOURHAWKID/anaconda2/bin”
The "normal" PATH setting must be before the anaconda directory in $PATH.install Anaconda in your home account and select "yes" for the installer to initialize Anaconda with conda init. That option modifies your ~/.bashrc so Anaconda is conveniently configured every time you log in, but the modification also causes graphical sessions to use dbus software supplied in Anaconda, which prevents them from starting. To solve this problem, edit your ~/.bashrc file to comment out all the lines in the "conda initialize" section. In the future, when you want to use Anaconda in a command prompt or in a job script, use the command required to activate it. For example, to activate a default installation of Anaconda3, use the following:
| Code Block |
|---|
exec "$($HOME/anaconda3/bin/conda shell.bash hook)" |
If your version of Anaconda is older or if the above command fails, you can still change your PATH variable in your shell or script to access it:
| Code Block |
|---|
export PATH="$HOME/anaconda3/bin:$PATH”