On Mon, Feb 12, Carlos E. R. wrote:
As ~/.xsession-errors was full of noise about browser problems, I killed firefox and chrome processes, which did work (pids no longer in `ps`, sound cut out from the movie I was watching in chrome), but the screen did not update (i.e. the browser windows were still there, unchanged).
Yes, that happens till the X process really dies. And -9 means it doesn't get a chance to restore the screen.
I suggest using "ps afxu | less -S" to find the hierarchy of processes and kill the parents.
But if the video driver is hung badly... maybe nothing restores it.
Yes, this is what I'm afraid of. Maybe next time I should try an `rmmod` - `modprobe` cycle.
No idea if keyboard freezing is *causing* the problem. To me it seems like more of a symptom. As stated in the original email, each of the screen, mouse and keyboard freeze together. There is simply no interactivity whatsoever.
Yes, it is a symptom. IMO :-)
How would this play with the theory that the video driver is hung? i.e., I hit CTRL-ALT-F2 and the machine "thinks" it gave me VT2, but I can't tell because the screen doesn't update? But if I typed my login, etc.. blind, I could get a terminal and send commands without having to ssh....sorry, brain hurting now. Thanks for the suggestions. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org