X2Go Bug report logs - #62
BadLength (poly request too large or internal Xlib

Full log

Message #28 received at 62@bugs.x2go.org (full text, mbox, reply):

Received: (at 62) by bugs.x2go.org; 19 Mar 2015 10:41:11 +0000
From Yvan.Broccard@swisscom.com  Thu Mar 19 11:41:09 2015
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,HTML_MESSAGE
	autolearn=ham version=3.3.2
X-Greylist: delayed 1342 seconds by postgrey-1.34 at ymir.das-netzwerkteam.de; Thu, 19 Mar 2015 11:41:08 CET
Received: from mail.swisscom.com (outmail110.swisscom.com [193.222.81.110])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id EF6E95DAA3
	for <62@bugs.x2go.org>; Thu, 19 Mar 2015 11:41:08 +0100 (CET)
Received: by mail.swisscom.com; Thu, 19 Mar 2015 11:18:46 +0100
From: <Yvan.Broccard@swisscom.com>
To: <62@bugs.x2go.org>
Subject:
Thread-Index: AdBiLhRCnKHPNQlyT5OhKrK+DSQYyw==
Date: Thu, 19 Mar 2015 10:18:45 +0000
Message-ID: <706c9b5e8e974430bb1d9a33e739ae35@SG001733.corproot.net>
Accept-Language: fr-CH, de-CH, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.57.139.57]
Content-Type: multipart/alternative;
	boundary="_000_706c9b5e8e974430bb1d9a33e739ae35SG001733corprootnet_"
MIME-Version: 1.0

[Message part 1 (text/plain, inline)]

We're encountering the same problem here.

gnome-control-center

(gnome-control-center:28288): Gdk-WARNING **: The program 'gnome-control-center' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 153 error_code 16 request_code 147 minor_code 1)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 7.6 (wheezy)
Release:        7.6
Codename:       wheezy

dpkg -l x2go\* nx\* gnome-session-fallback gnome-control-center | grep ^ii
ii  gnome-control-center                  1:3.4.3.1-2                                     amd64        utilities to configure the GNOME desktop
ii  gnome-session-fallback                3.4.2.1-4                                       all          GNOME Session Manager - GNOME fallback session
ii  nxagent                               2:3.5.0.28-0x2go1+git20141113.546+wheezy.main.1 amd64        NX agent
ii  x2goagent                             2:3.5.0.28-0x2go1+git20141113.546+wheezy.main.1 all          X2Go agent
ii  x2goserver                            4.0.1.18-0x2go1+git20141006.949+wheezy.main.1   amd64        X2Go server daemon scripts
ii  x2goserver-extensions                 4.0.1.18-0x2go1+git20141006.949+wheezy.main.1   all          X2Go server daemon scripts (extensions)
ii  x2goserver-fmbindings                 4.0.1.18-0x2go1+git20141006.949+wheezy.main.1   all          Generic (freedesktop-based) file manager bindings for X2Go
ii  x2goserver-pyhoca                     4.0.1.18-0x2go1+git20141006.949+wheezy.main.1   all          X2Go server daemon scripts (add-ons for pyhoca client)
ii  x2goserver-xsession                   4.0.1.18-0x2go1+git20141006.949+wheezy.main.1   all          X2Go server daemon scripts (Xsession runner)

Is there a workaround we could use to be able to launch gnome-control-center while you're working on a fix ?

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.