.ini files on client side incorrectly hold paths to server
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Linux, 4.1.0, remote server (multiple cases)
When a user does a remote connection using the GUI, the local .config/ParaView/ParaView4.1.ini file holds the remote plugins to load. This plugin list also includes hard coded paths to these remote plugin libraries. At the start of the config line, the remote server name is written, so ParaView can keep different servers straight.
This logic falls down when we are doing command line connects. The ParaView*.*.ini file then includes a server name of localhost, and all different connections use this line of the .ini file. Two issues - since paths are hard coded, they may be and often are wrong between different clusters. Second, we may not have the same plugins built between different clusters. This then makes the connection hang (seems somewhat random for this hang).
The workaround is to always delete the ParaView*.*.ini file before running.
Since this causes a hang, I am marking this bug as a crash.