Re: BadLength (poly request too large or internal Xlib length erro

[Ibrahim El-Shafei <shaffei softhome net>]

If I'm asking the wrong mailing list, kindly tell me which list to ask.

Thank you for your help in advance.

On Wed, 2003-06-18 at 20:56, Ibrahim El-Shafei wrote:
> Dear Sir,
> My system configuration is as follows:
> 1. System Used:	RedHat 8.0
> 2. GNOME-2.0
> 3. KDE-3.0.3
> 4. XFree86-4.2.0
> 
> The problem is that I tried to upgrade from GTK-2.0.0 to GTK-2.2.0.
> NOTE: CFLAGS= -O3 -march=i686 -finline-functions -funroll-loops
> 
> After the upgrade, I tried to login to my gnome session but, I couldn't
> see the desktop icon and when I press the main menu, I see blank menu
> with icons only. No applications run from the menu or the task bar
> icons, except the following:
> The Gimp 1.2.3
> Evolution 1.0.8
> 
> and here is the .xsession-errors after logging using gnome:
> 
> ==========================================================
> SESSION_MANAGER=local/shaffei.eth:/tmp/.ICE-unix/4076
> Loaded background '0x8098c18
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> The program 'nautilus' 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 46 error_code 16 request_code 156 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.)
> Multiple segmentation faults occurred; can't display error dialog
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> The program 'nautilus' 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 46 error_code 16 request_code 156 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.)
> Multiple segmentation faults occurred; can't display error dialog
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> The program 'nautilus' 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 46 error_code 16 request_code 156 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.)
> Multiple segmentation faults occurred; can't display error dialog
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> The program 'nautilus' 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 46 error_code 16 request_code 156 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.)
> Multiple segmentation faults occurred; can't display error dialog
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> The program 'nautilus' 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 46 error_code 16 request_code 156 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.)
> Multiple segmentation faults occurred; can't display error dialog
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> The program 'nautilus' 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 46 error_code 16 request_code 156 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.)
> Multiple segmentation faults occurred; can't display error dialog
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> FAMOpen failed, FAMErrno=0
> The program 'nautilus' 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 45 error_code 16 request_code 156 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.)
> The program 'nautilus' 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 46 error_code 16 request_code 156 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.)
> Multiple segmentation faults occurred; can't display error dialog
> 
> (magicdev:4142): GLib-GObject-WARNING **: cannot create instance of
> abstract (non-instantiatable) type `GtkWidget'
> 
> (gnome-panel:4146): GLib-GObject-WARNING **: cannot create instance of
> abstract (non-instantiatable) type `GtkWidget'
> The program 'gnome_segv' 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 43 error_code 16 request_code 156 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.)
> The program 'gnome_segv' 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 43 error_code 16 request_code 156 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.)
> 
> (pam-panel-icon:4148): Gdk-WARNING **: GdkWindow 0x1400002 unexpectedly
> destroyed
> =========================================================================
> 
> Also, after the installation of eog-1.0.3. I tried to run it but I
> receive the following error:
> 
> (eog:1767): GLib-GObject-WARNING **: cannot create instance of abstract
> (non-instantiatable) type `GtkWidget'
> 
> Thank you for your help in advance.
> 
> Best regards,
> -- 
> Ibrahim El-Shafei
> "HimaTech"
> 
> Love means having to say I'm sorry every 5 minutes.
> 
> _______________________________________________
> gnome-list mailing list
> gnome-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-list
-- 
Ibrahim El-Shafei
"HimaTech"

Love means having to say I'm sorry every 5 minutes.
-- 
Ibrahim El-Shafei
"HimaTech"

Love means having to say I'm sorry every 5 minutes.