Timothy Wilson wrote:
> 
> On Tue, 28 Nov 2000, Andy Zbikowski wrote:
> 
> > Try starting X from the command line (no display manager) with startx or
> > just X. Can you do this as root? Does startx work as a normal user?
> 
> I can use startx just fine.
> 
> > I'm going to make a guess that KDM is calling X and telling it to use
> > /etc/X11/XF86Config, when it should be using /etc/X11/XF86Config-4
> >
> > Check /etc/X11/kdm/Xservers.
> > /etc/X11/X -xf86config /etc/X11/XF86Config-4 should start the X server.
> > (/etc/X11/X is a sym link to /usr/bin/X11/XFree86)
> 
> After lots of comments, /etc/X11/kdm/Xservers contains:
> 
> :0 local /usr/bin/X11/X vt7 -deferglyphs 16
> 
> Clay asked about what the actual scripts looked like. Here they are:
> 
> galileo:/etc/X11/kdm# cat Xstartup_0
> #!/bin/sh
> #
> # /etc/X11/kdm/Xstartup_0
> #
> # This script is run as root after a user starts a session on :0.
> 
> set -e
> 
> # Call the global Xstartup script, if it exists
> if [ -x /etc/X11/kdm/Xstartup ]; then
>   /etc/X11/kdm/Xstartup || exit $?
> fi
> 
> # :0 specific startup commands go here
> 
> exit 0
> 
> Here's the /etc/X11/kdm/Xstartup file:
> 
> galileo:/etc/X11/kdm# cat Xstartup
> #!/bin/sh
> #
> # /etc/X11/kdm/Xstartup
> #
> # This script is run as root after the user logs in.
> # If this script exits with a return code other than 0, the user's
> # session will not be started.
> 
> PATH=$PATH:/usr/bin/X11
> 
> if grep -qs ^ignore-nologin /etc/X11/kdm/kdm.options; then
>   if [ -f /etc/nologin ]; then
>     if command -v xmessage > /dev/null 2>&1; then
>       xmessage -file /etc/nologin -geometry 640x480
>     fi
>   fi
> elif [ -f /etc/nologin ]; then
>   if command -v /usr/bin/X11/xmessage > /dev/null 2>&1; then
>     xmessage -file /etc/nologin -geometry 640x480
>   fi
>   exit 1
> fi
> 
> # insert a utmp entry for the session
> if grep -qs ^use-sessreg /etc/X11/kdm/kdm.options; then
>   exec sessreg -a -l $DISPLAY -u /var/run/utmp -x /etc/X11/kdm/Xservers
> $USER
>   # NOTREACHED
> fi
> 
> exit 0
> 
> Any ideas?
> 

Try running each script individually. And then make sure you have
everything it calls. I can't quite remember what I was missing, but I
got the same error. I tracked it down by running Xstartup by itself and
it told me what was actually causing it to error.