Firefox "config" file Rusts. How does one Default it?

[embedded]

Since Firefox uses the same configuration procedure in openSuSE 11.X as XP "about:config" many users have problems from the deterioration of this registry.

As we know it is saved in /home/<user>/mozilla/firefox/?????

This configuration registry rusts as it does in XP and extensions and hangs cause issues like really slow response. While some suggestions work there are configurations in the about:config from Firefox 1.X (including from bad extension) since I do not format /home.

A different hard drive or live cd provide a fast Firefox.

[bigtomrodney]

Why not just back up your bookmarks and create a new one? You can export your bookmarks through the Manage Bookmarks... dialogue and then restore them later to your fresh configuration. Of course you will have to reenter passwords and saved form information.

Close Firefox and then rename the config directory, either manually or with the command below.

mv ~/.mozilla ~/.mozilla.old

[embedded]

Why not just back up your bookmarks and create a new one? You can export your bookmarks through the Manage Bookmarks... dialogue and then restore them later to your fresh configuration. Of course you will have to reenter passwords and saved form information.

Close Firefox and then rename the config directory, either manually or with the command below.

mv ~/.mozilla ~/.mozilla.old

I quite agree! However I was hoping there is an elegant way that could serve all...... Certainly there should be judging by the frequency of comments about slow Firefox under Linux.

Quite frankly I would back up with foxmarks, opie and febe as well if I was going to rename (remove) the directory. There is a LOT of history there. I only have problems with Mozilla products that do an XP type registry.

[bigtomrodney]

How about running some routine maintenance on the sqllite database, see if that helps?

for f in ~/.mozilla/firefox/*/*.sqlite; do sqlite3 $f 'VACUUM;'; done

IF that's not enough, then I would suggest backing up bookmarks and going ahead. Sometimes you just have to cut your losses, if it's got bad data in there you can either take it out or have a fresh config.

[embedded]

How about running some routine maintenance on the sqllite database, see if that helps?

for f in ~/.mozilla/firefox/*/*.sqlite; do sqlite3 $f 'VACUUM;'; done

IF that's not enough, then I would suggest backing up bookmarks and going ahead. Sometimes you just have to cut your losses, if it's got bad data in there you can either take it out or have a fresh config.

This actually does work but takes out session manager and probably upsets something else since Firefox spends a LONG time first time after fixup. However it does clean out things.

So I would suggest first backing up /home/<user>/.mozilla/firefox/<config>.default/ about 70megabytes. (change the config name). Remove Session Manager extension. Back up bookmarks etc. Then away you go.