LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware Crash Behaviour (http://www.linuxquestions.org/questions/slackware-14/slackware-crash-behaviour-864461/)

boler 02-23-2011 02:26 AM

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.)

bgeddy 02-23-2011 04:25 AM

Quote:

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?
Quite possibly there may be a crash/loop in keyboard handling code but the mouse handler code still works - as seems to happen here.

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!

boler 02-23-2011 05:21 AM

ok thanks bgeddy. I haven't tried that one. I'll write it down and see if it works next time.

allend 02-23-2011 07:08 AM

Quote:

I know that it was caused by KDE's buggy code
Do not be too hasty in blaming KDE. This sort of instability may actually be due to the graphics driver.


All times are GMT -5. The time now is 10:09 AM.