Closed Bug 25277 Opened 25 years ago Closed 25 years ago

component.reg that we package up causes error

Categories

(SeaMonkey :: Installer, defect, P3)

Product:
SeaMonkey
Component:
Installer
Platform:
Other
Other
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: sdagley)

References

Details

(Whiteboard: [PDT+] Fix ready to check in.)

this happens with both the commercial and the mozilla builds from 1-27-2000 I think I sent mail about this to the hook, but I can't find it. granrose, dp and dougt jumped in with answers, so I'm cc'ing them the work around is to remove component.reg and let the app generate a new one. ************************************************** nsNativeComponentLoader: GetFactory(/builds/client/linux22/mozilla/mozilla/dist/bin/components/libxpinstall.so) Load FAILED with error: <unknown; can't get error from NSPR> **************************************************************************************************** nsNativeComponentLoader: GetFactory(/builds/client/linux22/mozilla/mozilla/dist/bin/components/libxpinstall.so) Load FAILED with error: <unknown; can't get error from NSPR> **************************************************
This was happening Tuesday or Wednesday. I think dougt was looking at it.
Dougt, this is a critical bug. We ship component.reg to avoid huge delays at install time and first time startp.
Assignee: leaf → dougt
Severity: normal → critical
Keywords: beta1
And doug, didn't you claim this was fixed yesterday.
Putting on PDT+ radar for beta1.
QA Contact: nobody → granrose
Whiteboard: [PDT+]
Target Milestone: M14
I have fixing in my tree. will check in tomorrow.
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] Fix ready to check in.
*** Bug 25543 has been marked as a duplicate of this bug. ***
QA Contact: granrose → leger
dunno how I ended up as QA contact for basic browser QA. punting to leger.
Windows and Unix are fixed. Assigning to sdagley for the mac
Assignee: dougt → sdagley
Status: ASSIGNED → NEW
Isn't this the same as #25629? In any case, as noted in that bug # my new computer ate my changes so I have to re-write them after re-formatting and reinstalling everything. Grrrrrr. ETA on the fix is now tomorrow afternoon.
Code checked in to let Mac Component Registry properly represent relative path components
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking Verified.
Status: RESOLVED → VERIFIED
Component: Browser-General → Installer
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.