Hi,
I’m in a somewhat unique environment — we run a preconfigured x2go as the only program for users connecting remotely to a Windows Server, so that they can then pick a session and go without having to set up ssh tunnels and configuring sessions directly. This is how our researchers connect via GUI to a remote pool of linux machines used for high-performance compute. It’s pretty critical that this service is up and running.
To make changes remotely, we log in to the server as administrator, change the system to use a custom X-Server of c:/Windows/System32/explorer.exe.
I am aware that this is probably doing a hundred things wrong already. I inherited this setup with no documentation, and the person who set it up has not worked here for several years.
Unfortunately, I think I must have made a typo in the custom X-server executable path.
The x2go client starts, immediately pops up a modal dialogue of “Can't start X Org Server, please check your installation”, and hitting OK on that closes x2go client (and thus logs off the connected user). Currently logged in users from before the typo are unaffected, and have long-running jobs that they need to continue, so I can’t just reboot the server to test because that would kick them all off, and if they can’t then smoothly reconnect it'd start a riot.
I’ve dug through the file system and registry to find where this setting is stored so I can revert to using the integrated X-Server, or at least disable the modal pop-up so I can change settings in the x2go client itself, but have had no luck.
If anyone has any ideas I’m all ears.
Cheers,
-Stew
--
Stew Wilson (he/him)
Computing Infrastructure Administrator, PPLS
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
