Closed
Bug 246935
Opened 20 years ago
Closed 20 years ago
Browser refuses to start after installing extensions
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: todd, Assigned: benjamin)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Downloaded Firefox .9 for Mac OS. Installed several extensions from the
update.mozilla.org website. System told me to restart, when I restarted, get
dialogue that it's finishing installation, but after several hours, it's still
not done.
Reproducible: Always
Steps to Reproduce:
1. Download new firefox (.9) for Mac
2. Install several extensions without restarting (all listed under developer)
3. Quit and re-start browser
Actual Results:
Browser hung with "Finishing Extension Installation' dialogue.
Expected Results:
Presented a status bar with the progress and then finished the isntallation and
allowed the browser to be useable
Reporter | ||
Comment 1•20 years ago
|
||
Note: had to make this bug report with .8 since .9 will not start. Also,
where's the pinstripe theme! :)
Confimed on 0.9 release, Mac OS X 10.2.8. Previous installed version of Firefox
0.8+ was about 2-3 weeks old.
Additionally, I can not undo this error. Firefox quits easily when this error
is displayed (it does not require a force-quit), but the error message reappears
on every startup. I have deleted every ~\library\Mozilla, ~\library\Firefox,
and/or ~\library\Phoenix directory (I don't recall which ones, but they are all
gone), deleted the Firefox application and shortcut, and reinstalled from a
freshly-destuffed disk image, but it still displays the 'finishing extension'
message on launch.
Todd,
What extentions? I installed on and it works just fine... maybe its one
extention that causes the problem... installing multiple extentions at a time...
as for pinstripe... you see version 2.0 of the theme... read more at
http://kmgerich.com/archive/000064.html
Oakwine,
Try:
~/Library/Application\ Support/Firefox
Reporter | ||
Comment 4•20 years ago
|
||
Removing my profile from the ~/Library/Application Support/Firefox directory did
allow Firefox to restart correctly.
The Extension manager was then blank, and when I would go to install an
extension, the initial drop down (do you want to install this extension, this
could install malicious software, etc) appears, but then after clicking install,
nothing happens.
When I try to click update, I get an error on the DOM extension update.
I am now downloading and retrying this whole process again.
A list of extensions:
User Agent Switcher (from update.moz.org)
Developer Toolbar (from update.moz.org)
JavaScript Console Status (from update.moz.org)
JS Control Extras (from update.moz.org)
Cute Menus (from update.moz.org)
WMLBrowser (from wmlbrowser.mozdev.org)
They were all installed before doing a restart of the browser.
Reporter | ||
Comment 5•20 years ago
|
||
I installed firefox .9 from scratch and did the same exact steps again, causing
the same exact result to appear.
this is easily reproduceable.
Reporter | ||
Comment 6•20 years ago
|
||
installing the extensions one-by-one has worked correctly.
Comment 8•20 years ago
|
||
(In reply to comment #6)
> installing the extensions one-by-one has worked correctly.
I have this same problem under Gentoo Linux - I could only get firefox to start
properly if I deleted my ~/.mozilla/firefox directory and started again from
scratch. I tried installing each extension individually (with a normal start
between installing each extension) and this worked fine for the first six
extensions or so, and then it broke again. Here are the extensions I was loading:
Adblock_0.5d2_nightly37_repackaged1.xpi
MozEX_1.0.7_pass1.xpi
Undo_Close_Tab_20040525.xpi
ChromEdit_0.0.5.1.1.xpi
OpenBook_1.0.xpi
DownloadWith_0.0.7.xpi
RadialContext_firefox.xpi
I can't remember which one caused it to break, but it certainly wasn't the
AdBlock, OpenBook, ChromEdit or RadialContext extensions because I was able to
use them.
Okay based on Comment #7 and Comment #8
Marking --> New
OS --> All
Platform --> All
Changing to Extention/Theme Manager
Status: UNCONFIRMED → NEW
Component: Startup and Profile System → Extension/Theme Manager
Ever confirmed: true
OS: MacOS X → All
Hardware: Macintosh → All
Comment 10•20 years ago
|
||
Tried to install some extensions and language translation on FC1 under root
account. After restarting under root all OK. If starting as non root user only
error window "XML parsing error...".
Reason: wrong permission (-r--------) on installed /usr/lib/firefox/chrome/*jar
files. Workaround: chmod 644 them
Comment 11•20 years ago
|
||
This evening I upgraded to the latest Firefox (Mozilla/5.0 (Windows; U; Windows
NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9), then installed the latest
Thunderbird, and then (from within Thunderbird) installed two or three new
extensions (the only existing one in FF was for TinyURL). This is on a WinXP
box, up to date but for SP2.
I experienced exactly the problem, closing Firefox and T-Bird, then on
re-opening FF finding:
Browser hung with "Finishing Extension Installation' dialogue.
After reading this page, and hoping to avoid a complete re-install, I deleted
the "extensions" folder under
C:\Documents and Settings\<username>\
Application Data\Mozilla\Firefox\Profiles\default.xxx\
Firefox then retarted fine.
Comment 12•20 years ago
|
||
I have something similar on Gentoo Linux (maybe another bug, but didn't feel
like opening yet another one...) with mozilla-1.7.2-r1. First I tried installing
lots of extensions as a user, but because of a bug you can only do this as root.
So I did. Everything ok, restarted as user. I didn't see all of the extensions
(only a few). Changed some preferences. Went back to root, and swa the rest of
the extensions there. Changed some preferences. Then back to the user-mozilla.
Which froze on start. I saw the very basic (classic though I had modern) layout
with the menu bar closed (??), but everything was frozen. Also got modern layout
once later on. Anyway, terminal showed that it gave some errors on .xul files
(extension related) that it couldn't open (permissions thing?) or overlay and
also a segfault error. I had to uninstall the hard way by deleting all those
.rdf's and .jar's from the extensions, in four places. Now I'm back in a working
mozilla, allthough I'm not sure if it will keep that way. What I think the cause
is: 1. root permissions, 2. make sure that the extensions work with my version
and are placed in the right place and that they work together, 3. what's this
overlay stuff?
No extensions yet for me, they seemed tempting though. BTW, the extensions from
gentoo (cal, gpg, ...) DO work.
ciao,
pjv
Comment 13•20 years ago
|
||
I have something similar on Gentoo Linux (maybe another bug, but didn't feel
like opening yet another one...) with mozilla-1.7.2-r1. First I tried installing
lots of extensions as a user, but because of a bug you can only do this as root.
So I did. Everything ok, restarted as user. I didn't see all of the extensions
(only a few). Changed some preferences. Went back to root, and swa the rest of
the extensions there. Changed some preferences. Then back to the user-mozilla.
Which froze on start. I saw the very basic (classic though I had modern) layout
with the menu bar closed (??), but everything was frozen. Also got modern layout
once later on. Anyway, terminal showed that it gave some errors on .xul files
(extension related) that it couldn't open (permissions thing?) or overlay and
also a segfault error. I had to uninstall the hard way by deleting all those
.rdf's and .jar's from the extensions, in four places. Now I'm back in a working
mozilla, allthough I'm not sure if it will keep that way. What I think the cause
is: 1. root permissions, 2. make sure that the extensions work with my version
and are placed in the right place and that they work together, 3. what's this
overlay stuff?
No extensions yet for me, they seemed tempting though. BTW, the extensions from
gentoo (cal, gpg, ...) DO work.
ciao,
pjv
Comment 14•20 years ago
|
||
Mac OS X, 10.3.8
Firefox 1.0.1
Firefox is installed under a different user and current user do not have write
access to firefox' install location.
Output from Console log:
*** getItemProperty failing for lack of an item. This means getResourceForItem
failed to locate a resource for aItemID (item ID =
http://ftp.mozilla.org/pub/mozilla.org/themes/saferfox_xpanded_2.3.1/saferfox_xpanded_2.3.1-2.3.1-fx.jar,
property = disabled)
*** getItemProperty failing for lack of an item. This means getResourceForItem
failed to locate a resource for aItemID (item ID =
http://ftp.mozilla.org/pub/mozilla.org/themes/saferfox_xpanded_2.3.1/saferfox_xpanded_2.3.1-2.3.1-fx.jar,
property = internalName)
JavaScript console:
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIFile.create]" nsresult: "0x80004005 (NS_ERROR_FAILURE)"
location: "JS frame ::
file:///Applications/Internet/Mozilla/Firefox.app/Contents/MacOS/components/nsExtensionManager.js
:: getDirInternal :: line 141" data: no]
Source File:
file:///Applications/Internet/Mozilla/Firefox.app/Contents/MacOS/components/nsExtensionManager.js
Line: 141
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIFile.create]" nsresult: "0x80004005 (NS_ERROR_FAILURE)"
location: "JS frame ::
file:///Applications/Internet/Mozilla/Firefox.app/Contents/MacOS/components/nsExtensionManager.js
:: getDirInternal :: line 141" data: no]
Source File:
file:///Applications/Internet/Mozilla/Firefox.app/Contents/MacOS/components/nsExtensionManager.js
Line: 141
Assignee | ||
Comment 15•20 years ago
|
||
There are several variations of this bug, but this one is old, and I have
committed a forceful workaround that will normally at least allow the browser to
start.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•