191101 - Try to fix a corrupt prefs.js

Status: RESOLVED DUPLICATE of bug 107264

(Core :: Preferences: Backend, enhancement)

Description

[Matthias Versen [:Matti]]

We got many bugs about a prefs.js corruption that results in a "startup
configuration warning".

Mozilla should first try to fix the corruption.
It's difficult to fix the corrupt file itself because you could loose data but
we we can use the "prefs.bak" .

If an error is detected in "prefs.js", display a warning if there is a "prefs.bak":
"An error occurred reading the startup configuration file (prefs.js).
Should Mozilla try to replace the corrupt file with a backup (prefs.bak) ? |
[Yes] ,[NO]"

YES: we replace the corrupt prefs.js with prefs.bak (and possible move the
corrupt "prefs.js" to "prefs.damaged")

If there is no "prefs.bak" display the current warning but please add the name
of the corrupt file (prefs.js)
I AM the admin but how should I know which file is damaged without this ?

Comment 1

[Conrad Carlen (not reading bugmail)]

Taking some of Brian's bugs.

Comment 2

[Will Small]

Attachment: Attached is a corrupted prefs.js file from Mozilla 1.3.1 Mac

This went unnoticed until the mail section stopped working.  Still have yet to
install 1.4 to see if that does anything different with it. I tried to delete
most of the seemingly junk data but it didn't fix the problem and I ended up
creating a  new user account for my client.  -Will

Comment 3

[Benjamin Smedberg]

There's another bug I marked P3 for fixing prefs.js corruption, so I'm going to close this one out as it doesn't track anything separate.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to Benjamin Smedberg  [:bsmedberg] from comment #3)
> There's another bug I marked P3 for fixing prefs.js corruption...

good to see there is potential interest in bug 107264