[X2Go-Dev] Windows 7 x2go Client Access Violation Connecting to CentOS 6 server using GNOME - Crashes in Latest Version Only

[OwN-3m-All]

Hi All,

I recently upgraded my x2go client from version 4.1.2.0 (Qt - 4.8.6)
to 4.1.2.2 (Qt - 4.8.6).

When I try to connect to one of my servers running CentOS 6 with the latest
updates, my x2go client on Windows 7 x64 SP1 immediately crashes.  In fact,
the connection never even makes it to the remote server for processing
according to the logs on the remote server, as the client forces the
connection closed (due to it crashing).

I even installed the debug version of the x2go client, and it doesn't
output anything of value before it crashes either.  Plus, it doesn't appear
to log anything to a file either?

After installing the old version of x2go in a different directory than the
newest version, I am able to connect just fine to the server using the old
x2go client version.

Something broke from the update.

What I can tell you is that I get this error message when debugging the
crash through Visual Studio:

https://serv1.dragndropz.com/user_images/2020_09_03/2256_oERSXY_2020-09-0316_29_08-x2goclientDebugging.png

Also, I was able to replicate this issue in a virtualized instance of
Windows 7 x64 SP1 via VirtualBox.

The CentOS 6 server I'm trying to connect to isn't running anything
special.  However, it is one of my oldest servers, and as a result, it is
the only server that is still running GNOME (usually I use MATE or XFCE).
I'm using a non-standard ssh port, a private key that uses a passphrase,
and "Session type" is set to GNOME.  I've disabled sound support and client
side printing support to make sure the crash didn't have anything to do
with these features.

Any chance someone could look into this further?  For now, I will just run
both versions of x2go side-by-side.

Thanks
OwN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.x2go.org/pipermail/x2go-dev/attachments/20200903/793b4c3e/attachment.htm>