Firefox problem (can't get rid of the default settings)
Firefox problem (can't get rid of the default settings)
Author
Discussion

FourWheelDrift

Original Poster:

92,391 posts

315 months

Saturday 28th April 2007
quotequote all
I had a few webpages trying to load, they weren't and I've found that if I close Firefox and restart they tend to load up. Only when I did it this time Firefox restarted in it's basic default skin and settings and even went through the process of reloading a few extensions.

Now my theme is set to Noia, yet it doesn't show, I still have the default theme. Same with the close icons on each tab. I changed the closebuttons option to get rid of them, the setting is the same but I still have the close icons on each tab.

Any ideas of what to do?

Is there a file somewhere that has become screwed that can be deleted?


I just created a new profile to see if that would fix it and the same problems exists.

Edited by FourWheelDrift on Saturday 28th April 20:29

FourWheelDrift

Original Poster:

92,391 posts

315 months

Saturday 28th April 2007
quotequote all
Right, bug fixed. In case anyone else gets this happen to them Firefox v2.0.0.3

Every setting was stuck on default and would not change to the options or choices I had previously. Without having to delete or remove any files I went through every theme, extension and add-on I had and ran an update on each one. None of them updated but after then choosing a new theme and restarting Firefox everything came back to normal. I would assume that when I closed Firefox something became corrupted (possibly one of the extensions) and Firefox thought it was a toaster and reverted to factory settings. Running the update might have rebuilt it's internal directory and sorted the problem. I think.

olivero

2,157 posts

240 months

Saturday 28th April 2007
quotequote all
Just had a look at the firefox site - it looks like they are still clearing out bugs on newer skins/themes. It might be worth seeing if you can update your copy of Noia 2.0 to version 3.371 (if this is not what you are running). I would think that passwords would not be affected or lost depending on the "skin" you are using. Good luck O

FourWheelDrift

Original Poster:

92,391 posts

315 months

Saturday 28th April 2007
quotequote all
olivero said:
Just had a look at the firefox site - it looks like they are still clearing out bugs on newer skins/themes. It might be worth seeing if you can update your copy of Noia 2.0 to version 3.371 (if this is not what you are running). I would think that passwords would not be affected or lost depending on the "skin" you are using. Good luck O


Was already running that, this problem also occured after everything had already been updated and Firefox was it's most up to date version. A problem not related to anything being an old version and not just after an update of anything. Completely random.


As an update, although the skin now works again the closebuttons option no longer works I cannot remove the close icon on every tab.


Edited by FourWheelDrift on Saturday 28th April 21:00

olivero

2,157 posts

240 months

Saturday 28th April 2007
quotequote all
odd.
just a shame you can't attack it with a hammer...

just a thought, have you cleared out cache and cookies ?

FourWheelDrift

Original Poster:

92,391 posts

315 months

Saturday 28th April 2007
quotequote all
olivero said:
odd.
just a shame you can't attack it with a hammer...


laugh

I've had that thought a few times recently. And often looking out my window and thinking how far I could get my computer down the garden.


I haven't cleared out the cache or cookies and won't because I will lose auto login settings I need (and don't want to have to resort to finding out where I have save the details). Besides I wouldn't have though they would effect the Firefox About:Config settings.

FourWheelDrift

Original Poster:

92,391 posts

315 months

Saturday 28th April 2007
quotequote all
I've just re-installed v2.0.0.3 and it didn't change it. Still can't get the closebuttons option I want to work. So it can't be a program problem.