Re: how to recover from an X lockup

2002-09-08 Thread Peter Whysall
Alvin Oga wrote: > hi ya travis > > - try the various(6) consoles > ( Alt-F1 ... alt-F6 ) > > - start X11 from console ( init 3 ) > and you can kill X by control-C on cosole No. This seems to have caused quite some confusion. This is NOT how X is started on a regular Debian install

Re: how to recover from an X lockup

2002-09-08 Thread Andreas Obermaier
On Wed, Sep 04, 2002 at 08:20:31PM -0400, Travis Crump wrote: > What is the recommended way to recover from an X lockup? Just a little > bit ago, X locked up on me(I was using a GL program and had multiple[2] > X's running) and I tried to get my system back by logging in remotely > and killing

Re: how to recover from an X lockup

2002-09-08 Thread martin f krafft
also sprach Peter Whysall <[EMAIL PROTECTED]> [2002.09.08.0314 +0200]: > I was just pointing out that Alvin's advice was valid for another Linux > distribution. > > Of course, it won't do anything at all to X on a regular Debian box. yup, so why post it in the first place, on debian-user??? --

Re: how to recover from an X lockup

2002-09-07 Thread Peter Whysall
On Sun, 2002-09-08 at 02:01, Mark L. Kahnt wrote: > On Sat, 2002-09-07 at 20:11, Peter Whysall wrote: > > martin f krafft wrote: > > > also sprach Alvin Oga <[EMAIL PROTECTED]> [2002.09.05.0322 +0200]: > > > > > >>- if you cann ssh-in > > >> if you can see X processes... kill those you dont

Re: how to recover from an X lockup

2002-09-07 Thread Mark L. Kahnt
On Sat, 2002-09-07 at 20:11, Peter Whysall wrote: > martin f krafft wrote: > > also sprach Alvin Oga <[EMAIL PROTECTED]> [2002.09.05.0322 +0200]: > > > >>- if you cann ssh-in > >>if you can see X processes... kill those you dont want > >>or blinly kill X11 > >>"init 3 ; s

Re: how to recover from an X lockup

2002-09-07 Thread Peter Whysall
martin f krafft wrote: > also sprach Alvin Oga <[EMAIL PROTECTED]> [2002.09.05.0322 +0200]: > >>- if you cann ssh-in >> if you can see X processes... kill those you dont want >> or blinly kill X11 >> "init 3 ; sleep 5 ; init 5" > > > since when does that kill X? It

Re: how to recover from an X lockup

2002-09-07 Thread martin f krafft
also sprach Alvin Oga <[EMAIL PROTECTED]> [2002.09.05.0322 +0200]: > - if you cann ssh-in > if you can see X processes... kill those you dont want > or blinly kill X11 > "init 3 ; sleep 5 ; init 5" since when does that kill X? -- martin; (greetings fr

Re: how to recover from an X lockup

2002-09-05 Thread Matthew Weier O'Phinney
--On Thursday, 05 September 2002, 09:00:45 AM, Colin Watson <[EMAIL PROTECTED]> wrote: > On Wed, Sep 04, 2002 at 06:22:18PM -0700, Alvin Oga wrote: > > - if you cann ssh-in > > if you can see X processes... kill those you dont want > > or blinly kill X11 > > "init 3 ; sle

Re: how to recover from an X lockup

2002-09-05 Thread Colin Watson
On Wed, Sep 04, 2002 at 06:22:18PM -0700, Alvin Oga wrote: > - if you cann ssh-in > if you can see X processes... kill those you dont want > or blinly kill X11 > "init 3 ; sleep 5 ; init 5" This is a Red Hat-ism. In Debian there's no difference between runlevels 3 a

Re: how to recover from an X lockup

2002-09-04 Thread Alvin Oga
hi ya travis - try the various(6) consoles ( Alt-F1 ... alt-F6 ) - start X11 from console ( init 3 ) and you can kill X by control-C on cosole - if your kb is dead... - unplug it and try again... - or try a different kb - if your mouse is dead.. - resta

Re: how to recover from an X lockup

2002-09-04 Thread R. Bradley Tilley (Brad)
Travis Crump wrote: > What is the recommended way to recover from an X lockup? Just a > little bit ago, X locked up on me(I was using a GL program and had > multiple[2] X's running) and I tried to get my system back by logging > in remotely and killing the X process with "kill -s KILL " of >

how to recover from an X lockup

2002-09-04 Thread Travis Crump
What is the recommended way to recover from an X lockup? Just a little bit ago, X locked up on me(I was using a GL program and had multiple[2] X's running) and I tried to get my system back by logging in remotely and killing the X process with "kill -s KILL " of the X that was frozen. Unfort