Iceweasel is sulking

JanVYW · 05-26-2009, 06:24 PM

Iceweasel stopped loading a few weeks ago on my user account but the sysmon thinks it is running. Same thing happens after a kill. I thought there must be a broken link following a crash but I find it runs happily in root. So what is likely to be set where that needs to be unset manually? Or (since it does seem slow to load) could it just be timing out but root is just that bit faster? In that case, where the xyz do I change time-out in KDE4? It's another thing that has vanished off the face the screen since 3.5!

AlucardZero · 05-27-2009, 11:17 AM

kill -9 it?

makuyl · 05-27-2009, 12:28 PM

kill -9 `ps aux|grep iceweasel|grep bin|awk '{print $2}'`
rm -i ~/.firefox/default/*/lock

JanVYW · 05-28-2009, 09:04 AM

It's not a kill problem. Sys monitor thinks it is running and kill gets rid of that. It still won't load though, although it does not think it is already running. I don't see why it should care if it is already running anyway. There could be reasons to launch two instances of the same browser (well there could but don't ask me what they'd be!). I'll have a look for that remove in .firefox though.

AlucardZero · 05-28-2009, 09:29 AM

run iceweasel from a console and paste the output

JanVYW · 05-28-2009, 01:21 PM

Good thinking! I never think to mix GUI and console apart from sometimes tracking console stuff in file browsers.

archtoad6 · 06-18-2009, 11:06 AM

What worked, please post the answer.

JanVYW · 06-20-2009, 09:54 PM

No idea! I just stopped using it and use Galeon because it can handle my emailer's HTML and Kazehakase because although it can't, it doesn't drop into automatic search mode in Yuku boards like Galeon. I'm more concerned with why I lost all sound after the KDE4 update.