From maciej@work.swmed.edu  Fri Mar 16 00:15:30 2018
Received: (at 1269) by bugs.x2go.org; 15 Mar 2018 23:15:32 +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=-4.2 required=3.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	SPF_HELO_PASS 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 EFC7B5DAE9
	for <1269@bugs.x2go.org>; Fri, 16 Mar 2018 00:15:29 +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 WOszv5ek06sj for <1269@bugs.x2go.org>;
	Fri, 16 Mar 2018 00:15:24 +0100 (CET)
Received: from swlxsmtp1.swmed.edu (swlxsmtp1.swmed.edu [199.165.152.166])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id C10E75DACF
	for <1269@bugs.x2go.org>; Fri, 16 Mar 2018 00:15:22 +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 1ewc5h-0001go-Cz
	for 1269@bugs.x2go.org; Thu, 15 Mar 2018 18:15:21 -0500
Received: from [129.112.10.165] (puma-1g.swmed.edu [129.112.10.165])
	by work.swmed.edu (Postfix) with ESMTP id 473B720061
	for <1269@bugs.x2go.org>; Thu, 15 Mar 2018 18:17:58 -0500 (CDT)
From: Maciej Puzio <maciej@work.swmed.edu>
To: 1269@bugs.x2go.org
Message-ID: <8f05569d-4d68-8163-81c4-3c4946d2452e@work.swmed.edu>
Date: Thu, 15 Mar 2018 18:15:21 -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: 4ee3b494223d39d3dd0b2fb4d8b7a7fd
Subject: X2go server crashes on Ubuntu 16.04

Philip, thanks a lot for the links to the Arctica bugs. 
While my symptoms are somewhat different (the crash occurs "automatically", just after the login, no window movement is necessary), 
the underlying cause is probably the same. As the Arctica report suggests, the problem is in fact dependent on the dual-screen 
configuration on the client side, and is solved by the fixed packages in the nightly build.