Closed
Bug 182579
Opened 22 years ago
Closed 22 years ago
Mozilla appears to drop the user configuration information. The browser settings are lost and the mail module tries to create new user accounts.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 193638
People
(Reporter: amathur, Assigned: asa)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 On startup, the following message is displayed "An error occured reading the startup configuration file. Please contact your administrator. Line 61: SyntaxError: missing ; before statement true);" on clicking ok, the browser starts, but with no user settings. When the mail application is started, it tries to create a new user account with new mailbox etc. Reproducible: Sometimes Steps to Reproduce: 1. Shut down mozilla 2. Restart mozilla 3. Actual Results: Most of the time, everything works fine. However, sometimes the error occurs. Expected Results: Load user settings. I am not sure, but my mail files may be the cause of the problem. I have almost 600 Megs of email and that could possibly be causing this problem. I have had this problem with most of the previous versions and nobody else mentioned this.
Likely it's because in your prefs.js, one of the lines ending with "true);" has a syntax error. Perhaps a missing comma, or the whole line before it is somehow broken. prefs.js is in your profile directory. Be very careful if editing it. Don't run mozilla during manual modifications. (They will be overwritten)
Updated•22 years ago
|
Blocks: profile-corrupt
Comment 2•22 years ago
|
||
-> worksforme Please do this : a) repair the prefs.js with a text-editor b) create a new mozilla profile
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Comment 3•22 years ago
|
||
Amitabh, did you modify your prefs.js file manually before the problem appeared? If not, I don't think such bugs should be closed WFM. Obviously, it does work for you, but any normal user running into it will consider it massive dataloss and be helpless about resolving it. Amitabh doesn't seems to be the only one with this problem (just yesterday, somebody from Adobe posted on .prefs with the same problem), so this problem needs to be fixed. Sorry for disturbing you triagers, you have a better overview, maybe I am missing something.
Comment 4•22 years ago
|
||
BenB : see also bug 172245, bug 132517 and also bug 191101
Comment 5•22 years ago
|
||
Bug 191101 is a workaround. Bug 132517 is unrelated, because "The truncated prefs.js seems properly formed" and no error, while we have a syntax error here, Bug 172245 is about brutal system shutdown (poweroff). Amitabh, was that the case here? If not, then none of the bugs apply.
If prefs.js contain a syntax error, everything after the error the isn't interpreted: bug 107264.
Comment 7•22 years ago
|
||
Mozilla shouldn't write faulty prefs.js files in the first place :-(.
True enough. But more specific bugs deal with that. And after bug 98476 was fixed, at least there is a backup of the file. (Several, if you prefer: See bug 98476 comment 71)
Comment 10•22 years ago
|
||
*** This bug has been marked as a duplicate of 193638 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
Updated•22 years ago
|
No longer blocks: profile-corrupt
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•