Slackware Crash Behaviour
Hi,
I was working on my desktop last night when my Slackbox froze up. Actually I was reading a pdf file in Okular when it happened. My question is a general one in that every time this happens my mouse and cursor movement functionality still works fine i.e., if I move my mouse around then the cursor moves on the screen as normal. However, the mouse buttons and keyboard loose all their power. Even Ctrl+ALT+F1 won't take me back to the shell and I am forced to reboot at the main switch. So if the computer can still operate the mouse position (in a crashed state) why then cannot it (be made to) operate any other emergency kill process functions? Regards, Tim (P.S. I know that it was caused by KDE's buggy code but KDE 4.4.3 is still part of Slackware 13.1 hence the thread title.) |
Quote:
Have you tried ctrl+alt+backspace to kill X? If this fails then try the "raising elephants" trick - i.e. hold down Ctr+printscreen and hit (slowly in turn) R,E,I,S,U,B - wait a little while for a result after each alpha key is hit. This nearly always gets through and will shut down stuff in a more orderly manner than just powering off or rebooting. Edit: Hope you see this edit - I got the above a bit wrong it's Alt+printscreen and hit (slowly in turn) R,E,I,S,U,B - sorry - I don't often have to do this! |
ok thanks bgeddy. I haven't tried that one. I'll write it down and see if it works next time.
|
Quote:
|
All times are GMT -5. The time now is 08:14 AM. |