2011/7/11 Dale <rdalek1...@gmail.com>: > Dale wrote: >> >> Bill Kenworthy wrote: >>> >>> On Mon, 2011-07-11 at 00:03 -0500, Dale wrote: >>>> >>>> Mark Knecht wrote: >>>>> >>>>> DAle, >>> >>> Hi Dale, not quite the same but something else to check - after my >>> 6monthly update round, I had two systems where FF refused to run - just >>> flashed up died. Erase .mozilla allowed one restart where I got a >>> window, any attempt to configure it killed FF. >>> >>> This is on gnome, not KDE so while symptoms differ, it may still be the >>> same root cause - some of the underlying packages needed rebuilding - it >>> was (maybe) nss and dev-lang/spidermonkey. Sorry, had a lot going on so >>> cant be more specific - it was strace that tipped me off (how I cant >>> remember). >>> >>> BillK >>> >> >> I'm going to try a clean directory for it here in a minute. I'm going to >> back up my whole home directory for good measure. >> >> I'm not holding my breath but I'll cross my fingers just in case. >> >> Dale >> >> :-) :-) >> > > OK. This is better. It seems to work. Can someone explain how a bad config > file in Firefox can cause a kernel panic? I thought things like this was > not possible? This sounds so windowish. o_O
We already explained you above in the other thread. That shouldn't be possible in a sane system. You haven't found the root of the problem, just the way to avoid it. The problem is in either the kernel (or one of its modules) or the hardware. Firefox (or any other userland program) has not the power to do this if the kernel doesn't allow it or a hardware failure doesn't screw up something. -- Jesús Guerrero Botella
