Hi BP,
This is a bug on certain platforms in the most recent Globus Connect Personal release. We have a version to fix for this and a couple of other issues which we're working on right now, and which we should release in the next couple of days.
If you're able to wait for a fix, that's the easiest solution.
However, we should be able to work around this (though it's a little bit tricky).
The trouble is with setting the library paths for different parts of the application -- one tool needs that `gt_amd64/lib/` directory, and others need to avoid it.
What should work is to set the library path and run the setup command in pure command-line mode. The commands would be
unset DISPLAY
export LD_LIBRARY_PATH="${PWD}/gt_amd64/lib:$LD_LIBRARY_PATH"
export GCP_SUPPRESS_STDERR=1
./globusconnectpersonal -setup --no-gui
This should start a pure command-line flow, which will print a browser link and wait for input.
Do a login flow with that link, copy-paste the resulting code into the prompt, and you should be guided through the rest of the setup process.
After that is done, in a fresh terminal (i.e. discarding those environment variables), you should be able to run `./globusconnectpersonal` and have it start as desired.
I can explain why the above options are necessary if you're curious, but we're also including some improvements in the upcoming release to these behaviors.
Another option is to download the older version of Globus Connect Personal (v3.0.4).
We'd have to provide you a bit more instruction to do that, and I think it might be best to contact
sup...@globus.org and we can work with you if that's the route you want to take.
Thanks & best,
-Stephen