2.0.0.8 Hoses Extensions
9 posts • Page 1 of 1
October 20th, 2007, 3:17 pm
After upgrading to 2.0.0.8 all my extensions are stuck in "will be installed when Firefox is restarted" despite having restarted/rebooted. A quick google shows I'm not the only one with this problem. I deleted the various extension.* files in my profile, no difference. I disabled all extensions using safe mode only to restart and find three-quarters of them missing. (The remaining few were disabled) Enabling the remaining ones and restarting resulted in some working extensions, but when I installed the missing ones I ended up where I started. Seems like one of my extensions is somehow disabling ALL extensions. Here's a list of what was working fine under 2.0.0.7...
Extensions (enabled: 26, disabled: 0): • Adblock Filterset.G Updater 0.3.1.2 • Adblock Plus 0.7.5.3 • Adobe Contribute Toolbar 1.0 • All-in-One Gestures 0.18.0 • Always Remember Password 0.6 • BugMeNot 1.3 • ColorfulTabs 2.0.7 • Diigo Toolbar for Firefox 1.0.2007101800 • DOM Inspector 1.8.1.8 • Download Statusbar 0.9.5.1 • ErrorZilla 0.2 • FireFTP 0.97.1 • FoxLingo 2.1.4 • GeckoTIP 1.0.0 • Gmail Notifier 0.6.1 • Greasemonkey 0.7.20070607.0 • IE Tab 1.3.3.20070528 • Image Zoom 0.3 • InfoLister 0.9f • Java Console 6.0.02 • NoScript 1.1.7.2 • Oboe for Firefox 1.6 • Save Link in Folder 1.3.4 • Session Manager 0.6.1.5 • Talkback 2.0.0.8 • Web Developer 1.1.4 Themes (4): • Blue Ice 1.2.4 [selected] • Firefox (default) 2.0 • Metal Lion - Vista 1.7.5 • Noia 2.0 (eXtreme) 3.371 Plugins (7): • 2007 Microsoft Office system • Adobe Acrobat • Java(TM) Platform SE 6 U2 • Microsoft® Windows Media Player Firefox Plugin • Mozilla Default Plug-in • Shockwave Flash • Windows Presentation Foundation
October 20th, 2007, 3:22 pm
This can be caused by one of files that contain details of installed extensions becoming corrupted.
Close Firefox, go to your profile folder and delete extensions.cache, extensions.ini and extensions.rdf Next open the extensions sub-folder within your profile folder, if there is a folder called staged-xpis delete it. When you next start Firefox the 3 extensions.* files will be re-created and in the process it will regenerate the list of installed extensions.
October 20th, 2007, 6:40 pm
ok im having the same problem--and i've already tried a number of things and nothing is fixing this problem---and like someone needs to fix this-so i can get back to a normal life.
October 20th, 2007, 6:44 pm
jkund17,
You were answered on your other thread/post that you created. Please stay with that thread for further discussion of your problem. Alcohol and Calculus don't mix. Never drink and derive.
October 20th, 2007, 6:53 pm
Thanks for the help. Unfortunately, as indicated in my post, I already completed those actions. (Actually, I left out that I'd looked for a staged-xpis, it didn't exist)
Thanks again, Drew
October 21st, 2007, 1:14 pm
I can add a few extensions to your list:
Add-ons Sidebar 0.2.2 Broadband Speedtest and Diagnostics 1.1 [may not be supported under 2.0.0.8] Download Statusbar 0.9.5.1 FlashGot 0.6.9.1 ServStats 0.5.0.5 Unplug 1.6.06 Update Notifier 0.1.5.3 Is this a bug or what? Not asking questions if you don't understand is dumb.
October 21st, 2007, 3:51 pm
My bad. After deleting extensions.rdf and staged-xpis (the only two of the four mentioned by Quarantine that were present), the software worked well.
Thanks for the help Quarantine. Not asking questions if you don't understand is dumb.
October 21st, 2007, 9:59 pm
*sigh*
FACT: I exited firefox and deleted the three extensions.* files. FACT: staged-xpis didn't exist FACT: I still had almost as many problems as I had extensions FACT: Just for giggles I decided to do it again today, and this time there WAS a staged-xpi's folder FACT: My disappeared extensions have returned and all are working?!? Sweet. Gotta love it when software makes you look like an idiot. Believe me or not I tried that fix before I ever posted in the first place, but for whatever reason it worked today. So cross me off the list of outstanding issues, but I stand by my claim that something screwy was introduced with 2.0.0.8. Regardless, thanks for all the suggestions, and thanks for the (newly reinstated) #1 browser on the market. Drew
October 22nd, 2007, 5:56 am
Glad it was fixed. Guess the like someone who needed like to get it like fixed, was you.
9 posts • Page 1 of 1
Who is onlineUsers browsing this forum: Alexa [Bot], RobertJ and 1 guest |
|