From maciej@work.swmed.edu  Wed Mar 14 23:16:44 2018
Received: (at 1269) by bugs.x2go.org; 14 Mar 2018 22:16:46 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=3.0 tests=BAYES_20,BODY_URI_ONLY,
	RCVD_IN_DNSWL_MED,SPF_HELO_PASS,URIBL_BLOCKED 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 D6B025DAE9
	for <1269@bugs.x2go.org>; Wed, 14 Mar 2018 23:16:44 +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 1KgpXRUfaRpD for <1269@bugs.x2go.org>;
	Wed, 14 Mar 2018 23:16:40 +0100 (CET)
Received: from swlxsmtp1.swmed.edu (swlxsmtp1.swmed.edu [199.165.152.166])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 00C155DACF
	for <1269@bugs.x2go.org>; Wed, 14 Mar 2018 23:16:39 +0100 (CET)
Received: from work.swmed.edu ([129.112.5.104])
	by swlxsmtp1.swmed.edu with esmtp (Exim 4.76)
	(envelope-from <maciej@work.swmed.edu>)
	id 1ewEhK-0004cu-8d
	for 1269@bugs.x2go.org; Wed, 14 Mar 2018 17:16:38 -0500
Received: from [129.112.10.165] (puma-1g.swmed.edu [129.112.10.165])
	by work.swmed.edu (Postfix) with ESMTP id CEA8020061
	for <1269@bugs.x2go.org>; Wed, 14 Mar 2018 17:19:19 -0500 (CDT)
From: Maciej Puzio <maciej@work.swmed.edu>
To: 1269@bugs.x2go.org
Message-ID: <7f6eb123-f991-a0f0-2f10-81311ffdc417@work.swmed.edu>
Date: Wed, 14 Mar 2018 17:16:38 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Scan-Signature: 8550f81978efdbf6f5d10beda515049b
Subject: X2go server crashes on Ubuntu 16.04

Seeing that my issue is indeed different from both other submitters, I decided to go ahead and post a separate report (bug 1272).
https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1272
The underlying cause may be turn out to be the same, so my new bug report may end up being a duplicate, or maybe not; difficult to say at this point.
Please everyone who suffers from a segfaulty nxagent after a recent update to post to one of these bug reports. We need to attract developers' attention.