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

[Message part 1 (text/plain, inline)]
Package: x2goagent
Version: 3.5.0.16-0

There seem to be gtk related issues with GTK in Wheezy.
You'll get an error similar to

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 155 error_code 16 request_code 147 minor_code 1)

Currently known are Eclipse:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=386955
https://wiki.archlinux.org/index.php/FreeNX#eclipse_crashes_when_editing_a_file

and the Gnome Control Center:
https://bugzilla.redhat.com/show_bug.cgi?id=827916
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/867631

-- 
Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter)
Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme)
Friedrich-Alexander-Universität Erlangen-Nürnberg
Martensstr. 1
91058 Erlangen

Tel   : +49 9131 85-25419
Fax   : +49 9131 85-28732
eMail : struebe@informatik.uni-erlangen.de
WWW   : http://www4.informatik.uni-erlangen.de/~morty

[smime.p7s (application/pkcs7-signature, attachment)]
[Message part 1 (text/plain, inline)]
Hello dear x2go devs.

There seems to be a problem with emesene and latest x2goserver/x2goagent.
It works on virt-viewer vnc console

Error output:
hteles@Code5:~$ emesene
Traceback (most recent call last):
  File "/usr/bin/emesene", line 34, in <module>
    emesene.main()
  File "/usr/share/emesene/emesene/emesene.py", line 861, in main
    main_method(Controller)
  File "/usr/share/emesene/emesene/gui/gtkui/__init__.py", line 29, in
gtk_main
    import gtk
  File "/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py", line 40,
in <module>
    from gtk import _gtk
ImportError: /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0: undefined symbol:
XRRFreeScreenResources

dpkg versions:

cups-x2go              3.0.0.4-0~62~precise1
x2goagent              2:3.5.0.16-0~278~precise1
x2goserver              3.1.1.6-0~610~precise1
x2goserver-extensions              3.1.1.6-0~610~precise1

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.1 LTS
Release:        12.04
Codename:       precise
root@Code5:~#

regards,

--

Helmer Teles

Web Page : http://hteles.wordpress.com

       .-.                   G N U
       /v\                 L I N U X
      // \\                   ---------
     /( _ )\        May The Source Be
    ^^     ^^             With You...

[Message part 2 (text/html, inline)]
[Message part 3 (text/plain, inline)]
_______________________________________________
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev
My friend and I are still affected by this bug on his system:

Debian GNU/Linux 7.5 (wheezy) 64-bit
nxagent 3.5.0.24-0x2go1+git20140508.472+wheezy.main.1
x2goserver 4.0.1.15-0x2go1+git20140403.847+wheezy.main.1
x2goserver-xsession 4.0.1.15-0x2go1+git20140403.847+wheezy.main.1
gnome-session-fallback 3.4.2.1-4
gnome-control-center 3.4.3.1-2

[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)]
[Message part 1 (text/plain, inline)]
Control: retitle -1 BadLength (poly request too large or internal Xlib  
length error)

On  Do 19 Mär 2015 11:18:45 CET, Yvan.Broccard wrote:

> 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.)
> gnome-control-center while you're working on a fix ?

We will get to fixing this issue soon.

Mike

-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]
[Message part 1 (text/plain, inline)]
Control: tags -1 moreinfo

HI again,

On  Do 19 Mär 2015 11:18:45 CET, Yvan.Broccard wrote:

> 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.)

I actually just tested this on a Debian jessie X2Go Server.

I use MATE desktop, so I launched gnome-control-center inside the MATE  
session from the command line.

If GLX in x2goagent is disabled [1], then gnome-control-center  
launches successfully.

If GLX in x2goagent is enabled, then gnome-control-center crashes,  
because it cannot load clutter. This, however, I consider a bug in  
gnome-control-center. If a GNOME application cannot load clutter due  
to lack of sufficient GLX support, the GNOME application (i.e.,  
gnome-control-center) should fall-back to a non-GLX mode.

Could you provide the exact steps for reproducing this issue?

Thanks,
Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]
Control: close -1

Closing due to inactivity. Feel free to reopen (by replying) in the 
unlikely event it is still neccessary.

Kind Regards,
Stefan Baur
-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

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

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