Closed Bug 199453 Opened 21 years ago Closed 21 years ago

configuration warning upon opening browser

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 193638

People

(Reporter: hchennings, Assigned: asa)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

I receive this configuration warning upon opening browser.
I will add an attachment so you can see it too.

 


Reproducible: Always

Steps to Reproduce:
1.Double click the browser icon.
2.Configuration Error
3.

Actual Results:  
Configuration Error

Expected Results:  
Mozilla should have opened to my home web page.

How do I attach a screen shot?
*** Bug 199454 has been marked as a duplicate of this bug. ***
Reporter: is your prefs.js file corrupted? Try replacing prefs.js in your
profile with prefs.bak, and if this fixes the problem, please resolve as invalid.
runtime issue -> B-G
Assignee: seawood → asa
Component: Build Config → Browser-General
QA Contact: granrose → asa
Please read bug 193638 (it could be also a damaged user.js if you created one)

(for attaching : open the bug link and use the "create new attachment link" in
the bug.)

*** This bug has been marked as a duplicate of 193638 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Screen shot is too big. 500kB
Where do I post it and provide a link?

I do not understand the exact details on fixing the problem.
I see some files need to be replaced. Could you provide the details.
I did an uninstall program from the control panel. I did
not inspect the details of any leftover files using
Windows Explorer.

Are you very busy with the bugs.
What is the schedule for a FINAL RELEASE?

Do you still have the problem ?
I couldn't read your response because I'm not cc'ed
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.