Re: X-windows not working anymore...
I did this and it worked great. Why is this? Thanks all for your help. "Gary L. Hennigan" wrote: > > "Damir J. Naden" <[EMAIL PROTECTED]> 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 > | > [EMAIL PROTECTED] > | > | 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 > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- -- -- -- -- The dumber people think you are, -- -- the more suprised they will be when you kill them. -- -- -- --
Re: X-windows not working anymore...
Hi Gary L. Hennigan; unless Mutt is confused, you wrote: > "Damir J. Naden" <[EMAIL PROTECTED]> 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 > | > [EMAIL PROTECTED] > | > | 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
Re: X-windows not working anymore...
"Damir J. Naden" <[EMAIL PROTECTED]> 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 | > [EMAIL PROTECTED] | | 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
Re: X-windows not working anymore...
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 > [EMAIL PROTECTED] 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 damir
Re: X-windows not working anymore...
> 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 [EMAIL PROTECTED]
Re: X-windows not working anymore...
Take a look at your ~/.xsession-errors file... I've usually found that it'll point me in the right direction. If that doesn't help, I'd be willing to do a little digging for you. I'd need you to run "startx [any-options-you-normally-use] >startx.out 2>&1", then email me the output from that along with ~/.xsession-errors, ~/.xsession (if it exists), and /etc/X11/XF86Config. On Fri, Feb 05, 1999 at 04:41:09PM -0600, Kelly Corbin wrote: > I recompiled the kernel putting the Unix domain sockets directly IN the > kernel (not in a module) and it doesn't give me that error message > anymore. Xwindows still doesn't work though and quits immediately after > starting just like there is no window manager. I have Afterstep, > Enlightenment, and TWM installed, and have tried every path possible in > the "window-managers" file but to no avail. Any more ideas. Thanks.
Re: X-windows not working anymore...
I recompiled the kernel putting the Unix domain sockets directly IN the kernel (not in a module) and it doesn't give me that error message anymore. Xwindows still doesn't work though and quits immediately after starting just like there is no window manager. I have Afterstep, Enlightenment, and TWM installed, and have tried every path possible in the "window-managers" file but to no avail. Any more ideas. Thanks. > Did you include "Unix domain sockets" when you configured your 2.2.1 > kernel? If not, you probably need to enable it and recompile. It it's > included as a module, you may need to add "alias net-pf-1 unix" to > /etc/modutils/aliases, then run "update-modules" as root. > > 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 > > reboot to my old kernel, it works again. It fails with the messages: > > X11Transocket open: socket() failed for local > > X11Transocket openCOTSclient: Unable to open socket for local > > X11TransOpen: transport failed for local / > > > > Am I missing something in my kernel or what? Any ideas anyone? I have > > rerun xf86config to no avail. Thanks. -- -- -- -- -- The dumber people think you are, -- -- the more suprised they will be when you kill them. -- -- -- --
Re: X-windows not working anymore...
Did you include "Unix domain sockets" when you configured your 2.2.1 kernel? If not, you probably need to enable it and recompile. It it's included as a module, you may need to add "alias net-pf-1 unix" to /etc/modutils/aliases, then run "update-modules" as root. On Thu, Feb 04, 1999 at 03:19:36PM -0600, Kelly Corbin 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 > reboot to my old kernel, it works again. It fails with the messages: > X11Transocket open: socket() failed for local > X11Transocket openCOTSclient: Unable to open socket for local > X11TransOpen: transport failed for local / > > Am I missing something in my kernel or what? Any ideas anyone? I have > rerun xf86config to no avail. Thanks.
X-windows not working anymore...
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 reboot to my old kernel, it works again. It fails with the messages: X11Transocket open: socket() failed for local X11Transocket openCOTSclient: Unable to open socket for local X11TransOpen: transport failed for local / Am I missing something in my kernel or what? Any ideas anyone? I have rerun xf86config to no avail. Thanks.
