--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: xlibs random crashes with an ATI Rage Mobility
- From: Emmanuel Fleury <fleury@cs.auc.dk>
- Date: Tue, 24 Feb 2004 16:09:53 +0100
- Message-id: <1077635390.8586.128.camel@rade7.s.cs.auc.dk>
Package: xlibs
Version: 4.3.0-2
Priority: standard
At random time my laptop refuse to start X and the only way to fix it is
to reboot.
This problem seems to be related to the graphic card :
ATI Rage Mobility M6 LY
Other people seems to have experimented this problem on other
distributions.
See: http://www.linuxquestions.org/questions/archive/14/2004/01/1/116108
The most interesting erro message that I get is from my
~/.xsession-errors file.
=====
/etc/gdm/PreSession//Default: Registering your session with wtmp and
utmp
/etc/gdm/PreSession//Default: running: sessreg -a -w /var/log/wtmp -u
/var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l :0 fleury
/etc/gdm/Sessions//Gnome: checking /etc/login.defs for option UMASK
/etc/gdm/Sessions//Gnome: /etc/login.defs: "UMASK" is "022"
/etc/gdm/Sessions//Gnome: checking /etc/login.defs for option ULIMIT
/etc/gdm/Sessions//Gnome: checking /etc/login.defs for option MAIL_DIR
/etc/gdm/Sessions//Gnome: /etc/login.defs: "MAIL_DIR" is "/var/mail"
/etc/gdm/Sessions//Gnome: using /etc/X11/Xsession.options for options
SESSION_MANAGER=local/hermes:/tmp/.ICE-unix/692
The program 'gnome-panel' 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 33 error_code 16 request_code 18 minor_code 0)
(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.)
Bug in window manager: Unexpected X error: BadLength (poly request too
large or internal Xlib length erro serial 592 error_code 16 request_code
18 minor_code 0)
The program 'metacity' 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 33 error_code 16 request_code 18 minor_code 0)
(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 33 error_code 16 request_code 18 minor_code 0)
(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 'battstat-applet-2' 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 33 error_code 16 request_code 18 minor_code 0)
(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-terminal' 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 33 error_code 16 request_code 18 minor_code 0)
(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 'evolution-alarm-notify' 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 33 error_code 16 request_code 18 minor_code 0)
(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 problem seems to be related to this:
serial 33 error_code 16 request_code 18 minor_code 0
As far as I got it:
error_code 16:
XProtoError.16 BadLength (poly request too large or internal Xlib length
error)
request_code 18:
XRequest.18:X_ChangeProperty
Seen in xc/lib/X11/XErrorDB (XFree 4.3.0 sources).
The request 18 might also be "ResizeRedirectMask" (but I'm really not
sure about it).
As I'm not an expert in debugging xlibs, I really would appreciate some
support for solving this bug which is irritating me. :-)
[fleury@rade7 src]$ dpkg -l | grep xlibs
ii xlibs 4.3.0-2 X Window System client libraries metapackage
ii xlibs-data 4.3.0-2 X Window System client data
ii xlibs-dev 4.3.0-2 X Window System client library development f
ii xlibs-pic 4.3.0-2 XFree86 static PIC libraries pseudopackage
ii xlibs-static-d 4.3.0-2 X Window System client library development f
ii xlibs-static-p 4.3.0-2 X Window System client extension library PIC
Regards
--
Emmanuel Fleury
Computer Science Department, | Office: B1-201
Aalborg University, | Phone: +45 96 35 72 23
Fredriks Bajersvej 7E, | Fax: +45 98 15 98 89
9220 Aalborg East, Denmark | Email: fleury@cs.auc.dk
--- End Message ---