Re: Classic Windoze lockup while in X (Gnome)
Joerg Johannes wrote:
Paul Scott wrote:
I just had something scary (to me) happen. I was in X (with Gnome)
working on my favorite LT WinModem problem. I was running Gnome Termnal
and GnomePad+. Potato 2.2.19pre17 with all other packages from the same
official CD image D/L'd.
As I was trying to find help with why I couldn't open a hidden file in
GnomePad+ I clicked on something, Gnome Terminal seemed to get the focus
with an I-Beam cursor (from GnomePad+ ?) and I had the symptoms of a
classic MS Windoze lockup. The mouse was dead. I could not open a
virtual terminal. I could not shut down X with Ctrl-Alt-Backspace.
Ctrl-Alt-Del did nothing.
I reset my CPU, rebooted to Linux and went to /var/log to see what I
could see. I don't yet know what logs to look for but sorting by time
seemed to only leave debug as relevant. This is the only line in the
Aug 15 00:52:29 joy gnome-name-server: server_is_alive:
cnx[IDL:help_browser/simple_browser:1.0] = (nil)
Any clues or suggestions of what to read would be appreciated.
Not really, but if you have the chance to, try to login via ssh
and try to kill some X and gnome processes, or just restart gdm.
Do you mean if the problem happens again or that I could have tried
those things when it happened. If the latter I could do nothing that I
knew of. Keyboard and mouse were both completely dead AFAICT. If you
know of another keystroke that might have worked please tell me. I
tried many other ctrl combinations than the ones I mentioned.
If the former (ignorant question on my part) how do I log in via ssh? I
doubt you meant that so the question would be is there any evidence of
the problem left on my system that I could examine?
This worked for me. It does not really fix the problem at all, but
at least you won't have to hard-reset you machine (which is generally
a bad idea).
As I said it was the only choice I could find. Before with any other
problems I have always been able to open a virtusl terminal and kill
something that is not working. That was the scary part. I thought I
would never have to reboot Linux for a reason like that.