X2Go Bug report logs - #703
x2goclient crash upon connection establishment

Full log

Message #19 received at 703@bugs.x2go.org (full text, mbox, reply):

Received: (at 703) by bugs.x2go.org; 15 Nov 2017 01:44:28 +0000
From ionic@ionic.de  Wed Nov 15 02:44:26 2017
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-2.0 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.1
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 586D05DACF
	for <703@bugs.x2go.org>; Wed, 15 Nov 2017 02:44:26 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Xh7ZwEITg6LJ for <703@bugs.x2go.org>;
	Wed, 15 Nov 2017 02:44:20 +0100 (CET)
Received: from mail.ionic.de (ionic.de [87.98.244.45])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 77C185DACA
	for <703@bugs.x2go.org>; Wed, 15 Nov 2017 02:44:20 +0100 (CET)
Received: from [10.30.44.7] (178.162.222.41.adsl.inet-telecom.org [178.162.222.41])
	by mail.ionic.de (Postfix) with ESMTPSA id 29EA34F006AE;
	Wed, 15 Nov 2017 02:44:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ionic.de; s=default;
	t=1510710260; bh=TyFMb/dql9Ub/dwb27XYcCnJmu5LAbRdj1kCLOE296s=;
	h=Subject:To:References:From:Date:In-Reply-To:From;
	b=kUBxshw/nwq+QtZBexmAx2mu9Ki9fXswT3/7fKH7jgq/TDpkrqoceT8Ul7d3mF//M
	 QIaVeg7/pD133P3DGOIZ2eZ5hrCcSG++wdbBhAy5JMqYv3aSXYvGBt9+EcXfbAJTom
	 h1bEdUUHKln8566wasSk7vFS/bWqIzax6qmkZqrQ=
Subject: Re: [X2Go-Dev] x2goclient crash upon connection establishment
To: Lianqi Wang <lianqiw@caltech.edu>, 703@bugs.x2go.org
References: <CAA631joC5CezUiSqRDqJy08dg4Ch_7BZ7SADeiSN2-Jc7=uDPg@mail.gmail.com>
From: Mihai Moldovan <ionic@ionic.de>
Message-ID: <f447f140-40b5-003d-d6c7-059ddc0d5f3d@ionic.de>
Date: Wed, 15 Nov 2017 02:44:19 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAA631joC5CezUiSqRDqJy08dg4Ch_7BZ7SADeiSN2-Jc7=uDPg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="cKtRD2KoSxdpLb64mJF9n8seOLeIowPUd"

[Message part 1 (text/plain, inline)]

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

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.