kubuntu crash
 

my box has been crashing about every two months.
Does anybody have any idea, what could be wrong?

Here's in more detail what happened at the last crash; the other crashes happened similarly:

my box crashed when viewing Google in firefox under kde in kubuntu.
I could still move the mouse around, but nothing else worked. no clicking, pressing Ctrl-Alt-F1 or Ctrl-Alt-Del or Ctrl-Alt-BackSpace didn't work either.
the keyboard LEDs wouldn't light up when Caps-Lock or Num-Lock were pressed either The mouse still looked like a hand (from hovering over a link) all the time.
The interesting part is really, that the mouse still moved nicely.

Thanks,
Sam

who says linux never crash?
i think certain linux is very screwed up, very worse,
like hell!
use pirated windows is much better.

> who says linux never crash?
> i think certain linux is very screwed up, very worse,
> like hell!
> use pirated windows is much better.

well thanks, this was very helpful...

futurist,
a) Please don't saotage 0 reply threads by posting when you have nothing to contribute to answering the Q posed -- You lessen the OP's chances of getting a quick answer.

b) Please don't post unsupported Linux bashing at all.

c) If you must post anti-Linux sentiments, please find an appropriate forum.

d) If you're so down on Linux, depart in peace.

e) Comparing 1 crash every 2 months to "reboot daily whether it needs it or not" is ludicrous. Granted "reboot daily whether it needs it or not" is not quite literally true, & at least partially tongue-in-cheek, but there is more than a large grain of truth in the aphorism.

f) Many of us are using GNU/Linux precisely to avoid the temptation or need to steal software. Many of us agree that if anyone deserves to have his product stolen, it is Bill Gate$; we just don't want to stoop to his level. If you haven't already, read The GNU Manifesto, especially "Why I Must Write GNU".

g) BTW, in case you don't recognize it, that is sarcasm in the reply shoffsta posted while I was composing this.


shoffsta,
I hope someone has a constructive idea for you & that this potential sabotage, I hope unintentional, does not hurt your chances of getting an A.

You have done an incredibly good job of describing an intermittent problem. One counter-Q: Since it's so rare, how much does this really matter, other than curiousity & a matter of principle?

> Since it's so rare, how much does this really matter, other than curiousity & a matter of principle?

1. well, if I'm working at something and the box crashes, I do lose data, which gets very annoying even if it's only once every two months.
2. I run my box at home as an ssh server which I use when I'm on a computer on campus. So if the computer crashes while I'm on campus I am locked out of ssh and have no access to my files till I get back and hard-boot. This means I'm screwed if I have and assignment due that night.
3. a good OS shouldn't crash, even if it's "only" once every two months.

-Sam

All good reasons, hope my curiosity didn't imply not taking your problem as serious or important.

Some more Q's for you:[list=1][*]When was the last crash?[*]You mention data loss, do you remember what else was running during any of the crashes?[*]Has it ever crashed when unattended? Can we add "ssh link also dies" to that thoughtful list of symptoms?[*]Have you tried looking at any log files? Don't ask me which ones, I just know it's a right thing to do.[*]How much have you done to "provoke" a crash? -- i.e. duplicate the problem.[/list=1]

I will be at our (HLUG) regular Wed. Linux Workshop tonight & will try to throw your problem out to the group.

which desktop version are u using 3.4.0

it maybe worth while upgrading to KDE 3.4.2

##KDE342
deb http://kubuntu.org/hoary-kde342 hoary-updates main
deb-src http://kubuntu.org/hoary-kde342 hoary-updates main

add the above to the etc/apt/sources-list

then update ...

there is no such thing as a non crashable OS. all OS's crash just some more than others. you have to remember its a human programming that OS to run and humans make mistakes. and some of time its user error that causes an OS to crash. i know one lady that shouldnt even be near a keyboard she keeps deleting her win32 file cause she thinks she dont need it (hard headed woman). there will always be errros and always be os;s that crash now given once every 2 months is alot. iv had mine crash 3 times this morning already its not even noon yet. so to say a good OS shouldnt crash well good luck finding one that will "never" crash. oh and it might help if we knew what version of kubuntu 4.10,5.04,5.10???

yes, I was using KDE 3.4.0 and I have only noticed crashes while working in KDE, although it might also happen otherwise, just not yet. I'm updating to 3.4.2 right now.

the last crash happened 09-18-2005.
other than the usual processes (artsd, kdeinit, ...) I was running kaffeine, kopete, vim and konqueror. nothing was scheduled in cron (except maybe update slocate. I don't remember the exact time of the crash)
I've never actually had this problem through ssh. I mentioned this because I had problems with this at the last power outage. I just assumed ssh wouldn't work if the box crashed this way again, but I don't know.
what logfiles would I check?

I'm using kubuntu hoary but I don't know exactly what version number (how do I find out), but I do run "apt-get dist-upgrade" every couple of days, so most of the software should be fairly up-to-date.

-Sam

hoary is 5.04

www.ubuntu.com will have it somewhere on it.

We're about to be in the middle of a hurricane here, will check logfile issue next week.

the computer crashed again, and no,I couldn't connect to ssh or apache.
It happened right after I switched from KDE to console on Ctrl-Alt-F6.
any ideas?

Don`t forget, hardare can crash too :)

My apologies, the hurricane is long gone, but I forgot to bookmark this thread & didn't remember to check on log files. Here's a suggestion: How long has it been since the last crash?

Is this important enough to start an "Incident file" to record the relevant details while they're fresh in your memory?

Have you tried to provoke a crash yet?

less -S~#15 /var/log/messages
gives me a lot of messages, however, there were no messages at the exact time of the last crash. hm.

and no I haven't been able to provoke a crash yet.
what's an "Incident file"? how do I set one up?

thanks,
Sam