Re: X-windows not working anymore...

["Damir J. Naden" <dnaden@inforamp.net>]

Hi Gary L. Hennigan; unless Mutt is confused, you wrote:
> "Damir J. Naden" <dnaden@inforamp.net> writes:
> 
> | Hi Pete Harlan; unless Mutt is confused, you wrote:
> | > > Question.  I recently upgraded my kernel from 2.0.36(I think) to 2.2.1. 
> | > > I am running slink(frozen) and now, my x-windows doesn't work.  If I
> | > 
> | > This happened to me, and .xsession-errors now says
> | > 
> | > /etc/X11/Xsession: line 47: syntax error near unexpected token `default)'
> | > 
> | > The bit of /etc/X11/Xsessions that reads
> | > 
> | >   case $1 in
> | >   failsafe)
> | >     if grep -q ^allow-failsafe $optionfile; then
> | >       if [ -x /usr/bin/X11/xterm ]; then
> | >         exec xterm -geometry +1+1
> | >       else
> | >         echo "Xsession: unable to launch failsafe X session: xterm not
> | >   found."
> | >         exit
> | >       fi
> | >     fi
> | >   default)
> | >     ;;
> | > 
> | > perhaps should have a ;; on the line before the "default)" line.
> | > (Haven't tried this myself yet.)
> | > 
> | > Good luck,
> | > 
> | > --
> | > Pete Harlan
> | > harlan@pointofchoice.com
> | 
> | I have just commented out the offending 'default)' line and it worked for
> | me. Does anyone know if this is a bad thing to do? I thought it was there
> | just as a comment sort of thing
> 
> In this case it won't hurt anything since the "default)" doesn't do
> anything. However, the correct solution is to put the ";;" in there.
> 
> Gary
> 
>

thanks for the info. I'll do that...

damir