From unknown Fri Mar 29 16:13:15 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#1321: [X2Go-Dev] Bug#1321: X Error: BadLength (poly request too large or internal Xlib length error) 16 Reply-To: Hannes =?UTF-8?Q?Kr=C3=B6ger?= , 1321@bugs.x2go.org Resent-From: Hannes =?UTF-8?Q?Kr=C3=B6ger?= Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Fri, 17 Aug 2018 11:15:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1321 X-X2Go-PR-Package: x2goserver X-X2Go-PR-Keywords: Received: via spool by 1321-submit@bugs.x2go.org id=B1321.153450443218042 (code B ref 1321); Fri, 17 Aug 2018 11:15:02 +0000 Received: (at 1321) by bugs.x2go.org; 17 Aug 2018 11:13:52 +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.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 20BCE5DAEB for <1321@bugs.x2go.org>; Fri, 17 Aug 2018 13:13:51 +0200 (CEST) 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 IjI8n2GOLmK7 for <1321@bugs.x2go.org>; Fri, 17 Aug 2018 13:13:44 +0200 (CEST) X-Greylist: delayed 1042 seconds by postgrey-1.35 at ymir.das-netzwerkteam.de; Fri, 17 Aug 2018 13:13:43 CEST Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::4]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 0163D5DACE for <1321@bugs.x2go.org>; Fri, 17 Aug 2018 13:13:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1534504423; s=strato-dkim-0002; d=kroegeronline.net; h=In-Reply-To:Date:Message-ID:From:References:To:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=MYIFXLBUOV71SfMZObvwHbC0nuuORqcTB/EKqunJGd0=; b=kmf6i+012HvsduamLQxbhUn/azv2OiCLbcJ3sNBFX3BAD/joAwkRL4ngRa31WnaGFA 4aQEDup+VZMoytNRy+NRGBiwAGiQF21GimFITJ+HRs932psTivJPqQd1ZpT5nVo5iyCU hEz5D8DXIqNzxLvRxdC7IgVAaw4fb+UDzFN2fLphDkCzhuMnxTEh1pq6niyUP6FRkXzU oNwlTI9vmjp3WO0BE08iCpcG9IR/Lve1SHd47PcbDd1JIaP2i8Lb9YHweJq+iIwI6X7z GcDq0SU4Z/paAf0jyZUozt4klkaeXVrs0bG/rcrG1JXoEcYZHkHFw+kS/L6W96r6GWWj 85zg== X-RZG-AUTH: ":JG0Ke0W7W/TTSgGbvYE0qyVmXpIsV+o8o4zBT/3H51ygBvJYrLPspGFOUEYD3WzR0NyOwWYe1gE=" X-RZG-CLASS-ID: mo00 Received: from [192.168.1.139] by smtp.strato.de (RZmta 43.18 AUTH) with ESMTPSA id Z08149u7HBDh0ma (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for <1321@bugs.x2go.org>; Fri, 17 Aug 2018 13:13:43 +0200 (CEST) To: 1321@bugs.x2go.org References: <92af9636-69fd-7a82-3061-e0a7b5faa18f@kroegeronline.net> From: Hannes =?UTF-8?Q?Kr=C3=B6ger?= Message-ID: <5d23baa7-6517-72e8-f32b-f03898923270@kroegeronline.net> Date: Fri, 17 Aug 2018 13:13:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US Dear Uli, thanks for the information. I will continue with the BIG-REQUEST enabled and see how it works. I would like to add that the problem appears since an update a few weeks ago (the software was installed through the x2go-stable repo from launchpad). Before that, everything worked fine. Is it possible to trace the change which lead to this problem? Regards, Hannes Am 17.08.2018 um 13:03 schrieb Ulrich Sibiller: > On Fri, Aug 17, 2018 at 12:44 PM, Hannes Kröger > wrote: >> ok, when I put >> >> X2GO_NXAGENT_DEFAULT_OPTIONS+=" +extension BIG-REQUESTS" >> >> into /etc/x2go/x2goagent.options then paraview starts without errors. >> >> But the comment says: >> "Disable BIG-REQUESTS, nx-libs does not implement this extension >> correctly. Leads to all sorts of weird crashes if left enabled." >> Is this still true? Do I have to fear all sorts of weird crashes? > Yes, unfortunately this is still true. I am unsure what exactly the > problems are. But we have apps that crash with the extension enabled. > And we have some apps that crash with the extension disabled ;-( > > Uli -- Grüße, Hannes Kröger Tel.: +49 160 90354853