The following is the output of startxfce4, please note that as a result no 
xfce4 windows except the quit screen can be launched without causing further 
errors, as well the panel never launches. I havle also included a full strace 
including children of xfce4-session, please find it attached. I verified that 
this problem occures both on xorg 6.8.1 and on 6.8.1.902 which is what I am 
running now. It also happend on xfce4 4.1.99.3, I did not get the chance to try 
previous RC's. 

Reproducible: Always
Steps to Reproduce:
1. Run startxfce4 on Gentoo/PPC64 
2.  
3.  
 
Actual Results:  
This is a pre-release version of the The X.Org Foundation X11. 
It is not supported in any way. 
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. 
Select the "xorg" product for bugs you find in this release. 
Before reporting bugs in pre-release versions please check the 
latest version in the The X.Org Foundation "monolithic tree" CVS 
repository hosted at http://www.freedesktop.org/Software/xorg/ 
X Window System Version 6.8.1.902 (6.8.2 RC 2) 
Release Date: 12 January 2005 
X Protocol Version 11, Revision 0, Release 6.8.1.902 
Build Operating System: Linux 2.6.11-rc1 ppc64 [ELF]  
Current Operating System: Linux Strife64 2.6.11-rc1 #1 SMP Sat Jan 15 00:47:11 
EST 2005 ppc64 
Build Date: 18 January 2005 
        Before reporting problems, check http://wiki.X.Org 
        to make sure that you have the latest version. 
Module Loader present 
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/Xorg.0.log", Time: Wed Jan 19 19:01:09 2005 
(==) Using config file: "/etc/X11/xorg.conf" 
Using vt 7 
/etc/xdg/xfce4/xinitrc: line 52: xscreensaver: command not found 
which: no dbus-launch in 
(/bin:/usr/bin:/usr/local/bin:/opt/bin:/usr/powerpc64-unknown-linux-gnu/gcc-bin/3.4:/usr/X11R6/bin:/opt/ibm-jdk-bin-1.4.2/bin:/opt/ibm-jdk-bin-1.4.2/jre/bin:/usr/qt/3/bin:/usr/kde/3.3/bin) 
SetClientVersion: 0 8 
SetKbdSettings - type: -1 rate: 30 delay: 500 snumlk: 0 
The program 'xfce-mcs-manager' received an X Window System error. 
This probably reflects a bug in the program. 
The error was 'BadValue (integer parameter out of range for operation)'. 
  (Details: serial 194 error_code 2 request_code 134 minor_code 15) 
  (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.) 
SetClientVersion: 0 8 
SetKbdSettings - type: -1 rate: 30 delay: 500 snumlk: 0 
The program 'xfce-mcs-manager' received an X Window System error. 
This probably reflects a bug in the program. 
The error was 'BadValue (integer parameter out of range for operation)'. 
  (Details: serial 194 error_code 2 request_code 134 minor_code 15) 
  (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.) 
 
** (xfwm4:9372): WARNING **: The window 0x40000c has not been restacked 
because the specified sibling 0x800004 was not found in our stack 
SetClientVersion: 0 8 
SetKbdSettings - type: -1 rate: 30 delay: 500 snumlk: 0 
The program 'xfce-mcs-manager' received an X Window System error. 
This probably reflects a bug in the program. 
The error was 'BadValue (integer parameter out of range for operation)'. 
  (Details: serial 279 error_code 2 request_code 134 minor_code 15) 
  (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.) 
 

Expected Results:  
A clean start.