Subject: Bug#703: [X2Go-Dev] x2goclient crash upon connection establishment

From: Mihai Moldovan <[email-masked]>
Date: Wed, 15 Nov 2017 02:44:19 +0100

Control: tag -1 moreinfo

On 12/16/2014 07:05 PM, Lianqi Wang wrote:
> Package: x2go client on Mac (10.10.1)
> Version 4.0.3.0
> 
> When the connection is established to my server, the x2go client immediately
> crash. It has happened many times and times to be more often recently after I
> updated the version of x2go client. The server is running x2goserver 4.0.1.18 on
> centos 7.
> 
> Here is the backtrace:
> 
> Process:               x2goclient [41285]
> Path:                  /Applications/x2goclient.app/Contents/MacOS/x2goclient
> Identifier:            x2goclient
> Version:               0
> Code Type:             X86-64 (Native)
> Parent Process:        ??? [1]
> Responsible:           x2goclient [41285]
> User ID:               501
> 
> Date/Time:             2014-12-16 09:45:10.840 -0800
> OS Version:            Mac OS X 10.10.1 (14B25)
> Report Version:        11
> Anonymous UUID:        D15E59D5-49FE-C920-0E6B-5B30CB94D859
> 
> Sleep/Wake UUID:       5A3B16A1-F98C-43FD-9F09-53C53032735E
> 
> Time Awake Since Boot: 43000 seconds
> Time Since Wake:       840 seconds
> 
> Crashed Thread:        0  Dispatch queue: com.apple.main-thread
> 
> Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes:       EXC_I386_GPFLT
> 
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   QtCore                        0x000000010e10732f QObject::disconnect(QObject
> const*, char const*, QObject const*, char const*) + 511
> 1   x2goclient                    0x000000010d083602
> ONMainWindow::slotProxyFinished(int, QProcess::ExitStatus) + 50
> 2   x2goclient                    0x000000010d1259f2
> ONMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1682
> 3   QtCore                        0x000000010e10918b
> QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2363
> 4   QtCore                        0x000000010e07f1c1 0x10dfba000 + 807361
> 5   QtCore                        0x000000010e0813d3 0x10dfba000 + 816083
> 6   QtCore                        0x000000010e10918b
> QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2363
> 7   QtCore                        0x000000010e15653c
> QSocketNotifier::activated(int) + 60

Is this still a problem with current versions?

Given that the code in question has not seen a lot of changes lately, I assume
that that's still the case, but please re-test and report back.

Mihai