Closed
Bug 302170
Opened 19 years ago
Closed 19 years ago
nsExtensionManager::_disableObsoleteExtensions - failure, catching exception so finalize window can close
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: carsten, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: firefox1.0.6-sparc-sun-solaris2.8.tar.bz2 & ../linux-i686/en-US/firefox-1.0.6.tar.gz *** nsExtensionManager::_disableObsoleteExtensions - failure, catching exception so finalize window can close *** loading the extensions datasource *** loading the extensions datasource after ~/.mozilla is greated, i get only the "*** loading the..." message Reproducible: Always Steps to Reproduce: starting firefox, no special steps Problem with solaris and linux builds (under solaris 9 and redhat 9) IMPORTANT: This is no duplicate of the bugs 246650, 259978, 272324, 294049 REASON: - New behaviour since 1.0.6, no problem with e.g. 1.0.4. No problems installing mozilla suite since the 0.9-versions until this new firefox. - I have full filesystem access at installing time (admin acl-rights), changing unix-rights (chmod) helps nothing. Tried all known hints descriped in some readmes or in the other bug-reports. SPECIALS: - I'm installing into a AFS filesystem, at installing time i use only one RW-volume, the readonly-volumes would be added later after the installation is working full. The user-homes are also in AFS. Only ACL-rights are relevant.
| Reporter | ||
Comment 1•19 years ago
|
||
additional information: tried also patch for "nsExtensionManager.js" from ralf utermann (https://bugzilla.mozilla.org/show_bug.cgi?id=272324) installation of mozilla-1.7.10 builds for solaris and linux work without any problems.
| Reporter | ||
Comment 2•19 years ago
|
||
german build is working.. http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/1.0.6/linux-i686/de-DE/firefox-1.0.6.tar.gz now make some further tests...
| Reporter | ||
Comment 3•19 years ago
|
||
i found the problem!
i copied our old firefox.js config to the new installation without changing
app.version and app.build_id keys! after changing this, i get only a two-line
message and firefox starts normal.
pref("app.version", "1.0.6");
pref("app.build_id", "2005072021");
firefox.js diff 1.0.4<->1.0.6:
-----------
->>>
57c57
< "1.0.6"
---
> "1.0.4"
61c61
< "2005072021"
---
> "2005051217"
128c128
< "1.0.6"
---
> "1.0.4"
-------------
the mozilla suite don't have this keys in the config. when installing mozilla i
make always a diff to the original config-files to test for changes before using
our custom config. with firefox i must have forgotten it and didn't thought
about that difference.
Severity: critical → minor
Comment 4•19 years ago
|
||
Resolving as WORKSFORME per reporter's comment.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•