From unknown Thu Apr 09 01:41:42 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#1272: nxagent crashes on Ubuntu 16.04, making x2go server unusable Reply-To: Maciej Puzio , 1272@bugs.x2go.org Resent-From: Maciej Puzio Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Thu, 15 Mar 2018 22:15:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1272 X-X2Go-PR-Package: nxagent X-X2Go-PR-Keywords: Received: via spool by 1272-submit@bugs.x2go.org id=B1272.152115189411790 (code B ref 1272); Thu, 15 Mar 2018 22:15:01 +0000 Received: (at 1272) by bugs.x2go.org; 15 Mar 2018 22:11:34 +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=-2.3 required=3.0 tests=BAYES_20,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 81F3B5DAE9 for <1272@bugs.x2go.org>; Thu, 15 Mar 2018 23:11: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 BIauWvJXF2CR for <1272@bugs.x2go.org>; Thu, 15 Mar 2018 23:11:21 +0100 (CET) X-Greylist: delayed 1415 seconds by postgrey-1.35 at ymir.das-netzwerkteam.de; Thu, 15 Mar 2018 23:11:21 CET Received: from swlxsmtp1.swmed.edu (swlxsmtp1.swmed.edu [199.165.152.166]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id A3B3F5DACF for <1272@bugs.x2go.org>; Thu, 15 Mar 2018 23:11:21 +0100 (CET) Received: from work.swmed.edu ([129.112.5.104]) by swlxsmtp1.swmed.edu with esmtp (Exim 4.76) (envelope-from ) id 1ewaiu-0005Vg-6K for 1272@bugs.x2go.org; Thu, 15 Mar 2018 16:47:44 -0500 Received: from [129.112.10.165] (puma-1g.swmed.edu [129.112.10.165]) by work.swmed.edu (Postfix) with ESMTP id 5C0B020061 for <1272@bugs.x2go.org>; Thu, 15 Mar 2018 16:50:21 -0500 (CDT) To: 1272@bugs.x2go.org From: Maciej Puzio Message-ID: <690513b1-3b10-4780-1192-f321e783174e@work.swmed.edu> Date: Thu, 15 Mar 2018 16:47:44 -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: dd9d27530f956c5d083e24d60cf26236 Good news! We have an upstream bug: https://github.com/ArcticaProject/nx-libs/issues/677 It appears that Arctica issue is exactly what I have been experiencing. I use KDE on two screens with different resolutions (1920x1200 and 1600x1200). X2goclient session uses only one of these displays, but the mere presence of two monitors on the client causes nxagent to crash on the server. I tested another client machine with one screen, and everything worked fine (i.e. I was able to open the session, and nxagent did not segfault). It does not matter whether I move the x2go session window, maximize it, and so on. All that matters is number of displays on the client and their relative size. (I did not test with two screens of equal size.) As the upstream bug suggested, I installed the x2go nightly packages, as explained here: https://wiki.x2go.org/doku.php/wiki:development:nightly-builds After that, the problem went away and dual-screen setup worked fine. So I guess the bug is fixed in nightly builds. As a side note, the number of bugs that show up in various Linux packages when using dual monitors has recently been so astounding that I am ready to give up and replace my setup with a larger single screen. Still, I can't force all my users to do so.