[WBEL-users] gnome-session errors

[Tom Cooper]

--=-dSBqFbxl4D+NdthsY1fP
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Mon, 2004-05-24 at 19:41, Ed wrote:
> > When I try to start X on the console, X dies after gnome-session tanks.  
> > gnome-session complains about failure to read (or write, I can't 
> > remember right now) the correct number of bytes.
> 
> Can you post a complete error message?

Full details are in the attached file, but the meat of the error is
below:

The program 'gnome-session' 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 675 error_code 16 request_code 153 minor_code 20)
> 
> > 
> > I'd write it off as a corrupt library, but I can run VNC server with 
> > gnome-sessions and there are no complaints.
I realized after writing this that it is not accurate.  When I launch
gnome-session within the VNC session, my fonts get corrupted - totally
unreadable.  X continues to operate, and killing gnome-session does not
fix the problem.

I'm stumped.

> > 
> > If I switch to twm, X starts and operates perfectly (although it is a 
> > bit....less featureful than Gnome.)
> > 
> > Anyone have a suggestion about how to further troubleshoot?  I've poked 
> > around on Google, and the mentions of this sort of error on the gnome 
> > archives point to problems that I don't have.
-- 
Tom Cooper <tcooper@starpower.net>

--=-dSBqFbxl4D+NdthsY1fP
Content-Disposition: attachment; filename=startxerror.txt
Content-Type: text/plain; name=startxerror.txt; charset=iso-8859-1
Content-Transfer-Encoding: 7bit



XFree86 Version 4.3.0 (Custom Build: 4.3.0-62.EL)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.21-9.0.1.EL i686 [ELF] 
Build Date: 14 May 2004
Build Host: bob.whiteboxlinux.org
 
	Before reporting any problems, please make sure you are using the most
	recent XFree86 packages available from Red Hat by checking for updates
	at http://rhn.redhat.com/errata or by using the Red Hat Network up2date
	tool.  If you still encounter problems, please file bug reports in the
	XFree86.org bugzilla at http://bugs.xfree86.org and/or Red Hat
	bugzilla at http://bugzilla.redhat.com

Module Loader present
OS Kernel: Linux version 2.4.21-9.0.3.EL (buildsys@bob) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20)) #1 Sat Apr 24 22:04:25 EDT 2004 
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Tue May 25 09:05:20 2004
(==) Using config file: "/etc/X11/XF86Config-4"
	Trio3D -- Display is on...turning off
	Trio3D -- S3VNopAllCmdSets: SubsysStats#1 = 0x20007f80
	Trio3D -- S3VNopAllCmdSets: state changed after 0 iterations
	Trio3D -- S3VNopAllCmdSets: SubsysStats#2 = 0x1f815f80
	Trio3D -- GE was on ST#1: 0x20007f80 ST#2: 0x20007f80
	Trio3D -- S3VNopAllCmdSets: SubsysStats#1 = 0x20007f80
	Trio3D -- S3VNopAllCmdSets: state changed after 0 iterations
	Trio3D -- S3VNopAllCmdSets: SubsysStats#2 = 0x1f807f80
	Trio3D -- S3VNopAllCmdSets: SubsysStats#1 = 0x20007f80
	Trio3D -- S3VNopAllCmdSets: state changed after 0 iterations
	Trio3D -- S3VNopAllCmdSets: SubsysStats#2 = 0x1f815f80
localhost being added to access control list
dsmon-l2 being added to access control list
dsmon-s2 being added to access control list
localhost being added to access control list
dsmon-l2 being added to access control list
dsmon-s2 being added to access control list
SESSION_MANAGER=local/tcooper-87057.marriott.com:/tmp/.ICE-unix/17970
GetModeLine - scrn: 0 clock: 121500
GetModeLine - hdsp: 1152 hbeg: 1216 hend: 1344 httl: 1568
              vdsp: 864 vbeg: 865 vend: 868 vttl: 911 flags: 9
The program 'gnome-session' 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 675 error_code 16 request_code 153 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.)

waiting for X server to shut down 	Trio3D -- Display is on...turning off
	Trio3D -- S3VNopAllCmdSets: SubsysStats#1 = 0x20007f80
	Trio3D -- S3VNopAllCmdSets: state changed after 0 iterations
	Trio3D -- S3VNopAllCmdSets: SubsysStats#2 = 0x20015f80
	Trio3D -- GE was on ST#1: 0x20007f80 ST#2: 0x20007f80
	Trio3D -- S3VNopAllCmdSets: SubsysStats#1 = 0x20007f80
	Trio3D -- S3VNopAllCmdSets: state changed after 0 iterations
	Trio3D -- S3VNopAllCmdSets: SubsysStats#2 = 0x1f807f80
	Trio3D -- S3VNopAllCmdSets: SubsysStats#1 = 0x20007f80
	Trio3D -- S3VNopAllCmdSets: state changed after 0 iterations
	Trio3D -- S3VNopAllCmdSets: SubsysStats#2 = 0x1f807f80


Window manager error: Unable to open X display :0.0

--=-dSBqFbxl4D+NdthsY1fP--