hello,

I know I'm running a software stull under development but I'm curious ;)

I run a gentoo Linux box and there is a package called XFree-4.2.99
available which I build and installed.

Now I have a strange issue:
I can run plain X-Apps and i.e Mozilla just fine and also Gnome-1.4 apps
like Evolution run without problems.

But any Gnome-2 app stops with this error:

Gdk-ERROR **: The program 'gdmlogin' 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 53 error_code 16 request_code 157 minor_code 20) 
(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.) 
aborting... 


Gdk-ERROR **: The program 'rep' 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 39 error_code 16 request_code 157 minor_code 20) 
... 

(Details: serial 51 error_code 16 request_code 157 minor_code 20) 


etc.


same message every time, only the serial is different.

now which part of my system might cause this trouble?
where should I start to look ... 

I tried to run i.e. gdmlogin with gdb
Did not get much info out of it ...


Starting program: /usr/bin/gdmlogin 
[New Thread 1024 (LWP 29997)]

Gdk-ERROR **: The program 'gdmlogin' 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 53 error_code 16 request_code 157 minor_code 20)
  (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.)
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread 1024 (LWP 29997)]
0x40a38491 in kill () from /lib/libc.so.6
(gdb) bt
#0  0x40a38491 in kill () from /lib/libc.so.6
#1  0x40438323 in pthread_kill () from /lib/libpthread.so.0
#2  0x4043886b in raise () from /lib/libpthread.so.0
#3  0x40a39c99 in abort () from /lib/libc.so.6
#4  0x40907891 in g_logv () from /usr/lib/libglib-2.0.so.0
Cannot access memory at address 0x2


After compiling this version of XFree i recompiled glib, gtk+ and some
font relatet libs ... still the same errors :(

any help?

thanks


-- 
Jens Ansorg <[EMAIL PROTECTED]>

_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Reply via email to