November 14, 2004 16:04 | MacStuff / WebTech

Firepoop

I can't seem to get Firefox to work on my machine.

Immediately after launch, the only item in the top Menu is "Firefox" (no "File, Edit etc...") and essentially the keyboard is disabled (I can't type a URL into the Address box, or into any form elements).

I poked around a bit yesterday and at seemingly totally random, unreproducable times, the menu bar reappears and the keyboard is reactivated, though sporadically. This "reawakening" would happen after sometimes opening a new window, opening a link in a new tab, closing a tab, closing all windows and clicking on Firefox in the Dock to force it to open a new window...

This is not new to me though. I haven't been able to run Firefox on this machine for months. Yes, I have deleted all Preferences and caches and anything and everything related to Firefox (or any of it's myriad previous codenames).

Believe it or not I have even wiped my hard drive and reinstalled a clean OS, just to get Firefox to work. To. No. Avail.

Frustrating because I know I am missing out on something good. In my poking around yesterday I installed a bunch of very very interesting extensions and tools and such. But the bloody thing only works for me 20% of the time, so it's a no-go.

On a tangentially related note, the DNS issues I have been experiencing lately with all webbroswers, where the browser times out saying "Address not found" only to find it as soon I refresh, seems to be fixed by running the built-in system cleanup CRON jobs (daily, weekly, monthly). These scripts run on their own IF your machine is on and awake at the time they are set to run (early morning apparently). This means many many people never, or very very rarely have them run.

For you fine folks, here is some info on how to do this.

Comments

Pour les problèmes de DNS, j'ai eu la m√™me situation voici quelques semaines et j'ai trouvé ceci comme seul moyen pour y remédier: ne pas laisser vide le champ ¬´DNS servers¬ª dans Network. Juste √† lui donner une adresse IP d'un serveur DNS et hop! le problème est disparu.