Below are some of the more common causes of problems when logging into the Linux Lab machines, either remotely or in person (ECE room 361).

A session already exists on that specific workstation (remote only)

If you already have another graphical login session running on a specific machine (either in person or remote), attempting to create a new RDP session to that machine will usually fail.

The simplest test for this is to pick a machine you have never logged into, and try connecting to it. If that works, your connection issues are probably caused by an already existing session.

Issues with your shell’s login files (in-person or remote)

If there is some problem with one or more of your login files (e.g .bash_profile, .bashrc, .cshrc, .profile, .zshrc), that can cause your login session to abort.

This happens quite often, especially for people who’ve tried to configure their account to auto-switch to tcsh at login. The problem can be as trivial as the file generating text output because of an echo statement, or an error message occurring while a line in the file is executing.

The test for this is to move all of those login files out of the way (temporarily rename them, or move them to a temporary subdirectory) and then see if you can successfully connect.

Corrupted Gnome profile (in-person or remote)

Occasionally we have found that the desktop files in a person’s home directory which are used by Gnome (the desktop manager for in person and RDP connections) get corrupted.

The solution to this is to have us re-create your home directory. When we do this, we copy all of your existing files into a subdirectory of your new home directory, so this shouldn’t result in a loss of any data.

Resetting your home directory does require ending all of your existing sessions to every Linux Lab machine beforehand.