On Fri, Jan 24, 2020 at 9:50 AM Tristan Miller <psychonaut@nothingisreal.com> wrote:
By the way, your instructions suggest using a wrapper script that sets LD_LIBRARY_PATH when invoking GLX applications. Is there any reason that I can't just export LD_LIBRARY_PATH globally in my X2Go sessions? That is, is there any danger/disadvantage to using Mesa's libGL when running non-GLX applications over X2Go? I ask because just setting LD_LIBRARY_PATH in my .bashrc (within an if block that checks for $X2GO_AGENT_PID or $X2GO_SESSION) will be easier than remembering to manually invoke a wrapper for GLX applications.
Do as you like. ;-) Generally speaking I don't like setting LD_LIBRARY_PATH (or even LD_PRELOAD) globally (t.i. session-wide) because I have seen many applications that fiddle with the LD_LIBRARY_PATH themselves and are not prepared for the variable already being set. So they either break that functionality or fail with weird errors. If you explicitly called such an application with a wrapper you are aware that you did just that and can easily try the application without the wrapper. Global variables tend to be forgotten...
Uli