Xdmx - BadLength Error

Boris Neubert neubert at inf.uni-konstanz.de
Tue Feb 6 12:36:44 PST 2007


I hope it is the right place to ask problems regarding the xdmx server.
My system configuration is:
Intel PIV / Linux (Debian) 2.6.18-3
2 (Head) Xserver 7.1.1 and one Xdmx 1.2.20040630

After starting xdmx 

-Xdmx :2 -display atlas_1:0 -display atlas_2:0 +xinerama -noglxproxy

everything is fine (x-server gray pattern) and starting x applications like
xclock xeyes etc. works fine.
Starting twm or kde works. However most applications (e.g. gnibbles) show an
BadLength error messages:

The program 'gnibbles' 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
  (Details: serial 54902 error_code 16 request_code 144 minor_code 30)
  (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 --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

This error message shows up even with the twm only setup and xdmx seems to
restart (log attached).
Maybe somebody can point me in the right direction or has observed similar


Boris Neubert
University of Konstanz/ Germany
Computer Graphics and Media Design
room:   Z706
phone:  0049 (0) 7531 88 2768
email:  neubert at inf.uni-konstanz.de  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xdmx.log
Type: application/octet-stream
Size: 59136 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20070206/ff4f8455/attachment.obj>

More information about the xorg mailing list