Subject: Bug#1321 closed by Mihai Moldovan <[email-masked]> ()

From: [email-masked] (X2Go Bug Tracking System)
Date: Thu, 29 Nov 2018 05:15:02 +0000

This is an automatic notification regarding your Bug report
which was filed against the x2goserver package:

#1321: X Error: BadLength (poly request too large or internal Xlib length error) 16

It has been closed by Mihai Moldovan <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mihai Moldovan <[email-masked]> by
replying to this email.

-- 
X2Go Bug Tracking System
Contact [email-masked] with problems

From: Mihai Moldovan <[email-masked]>
To: [email-masked]
Date: Thu, 29 Nov 2018 06:04:31 +0100

tag #1321 pending
fixed #1321 4.1.0.3
close #1321
thanks

Subject: X Error: BadLength (poly request too large or internal Xlib length error) 16
From: Kröger, Hannes <[email-masked]>
To: [email-masked]
Date: Fri, 17 Aug 2018 09:55:25 +0200

Package: x2goserver
Version: 4.1.0.2-0~1642~ubuntu16.04.1

When the 3D viewing software paraview is executed in a x2go session, it
does not start, but yields the error below:
$ paraview
X Error: BadLength (poly request too large or internal Xlib length error) 16
  Major opcode: 18 (X_ChangeProperty)
  Resource id:  0x30001da
This problem does not appear in older versions of x2go. I could not find
a workaround for the problem. Any hints are welcome.
OS: Ubuntu 16.04 Xenial
Paraview - Version 4.4.0
NXAGENT - Version 3.5.99.16