Closed
Bug 161164
Opened 22 years ago
Closed 20 years ago
Mozilla Nightly Forgot All Settings
Categories
(Core Graveyard :: Profile: Migration, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 193638
People
(Reporter: MattCoe, Assigned: sspitzer)
References
Details
(Keywords: dataloss)
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1b) Gecko/20020804 BuildID: 2002080419 Hey, I just downloaded the nightly at about 1:45 AM GMT-5 when I was working on a website and discovered that the new build had somehow forgotten /all/ of my settings. It was installed on top of the old build, and no other nightly's done this. Reproducible: Didn't try, don't know how I would. Steps to Reproduce: 1. Set some settings in a previous build. 2. Download the nightly for the 2002080419 build. 3. Open up Mozilla and try to do anything. Actual Results: All my font settings, and, well, everything reverted to defaults. My mail profiles have been ignored; I don't want to reinstall them by hand. Expected Results: Was expecting to have everything continue working as it previously had. Additional information? Ummm...the new icons are hideous and too Netscape-y. I liked seeing Mozilla in the corner.
Comment 1•22 years ago
|
||
Do you saw this after you started the new build or later ? If later : Do you use quicklaunch ?
Keywords: dataloss
Basically right after I installed the new build. I was working with the browser at the time, so I didn't notice until I decided to check my mail. And yes, I am kind of a Quicklaunch junkie, although I've noticed that Quicklaunch itself seems a little buggy. I was checking through the release notes for 1.1b and saw something about there being a known bug in Quicklaunch, and I think I read the bug report, but it didn't seem related. Did my decision to activate Quicklaunch on install affect this? (I've hand-hacked my email settings back in since I reported this bug... I noticed that prefs.js seems to have been rewritten by the installer.)
Comment 3•22 years ago
|
||
Looks like a duplicate of bug 155080. reporter can you confirm?
Bug 155080 looks similar... but this happened to me every time I'd try to start Mail after I installed the nightly. Kinda like 155080, symptoms are the same but the trigger's different. That bug says it happened sporadically, mine started right after install.
Comment 5•22 years ago
|
||
I have seen other reports of this- assigned to various components- I am trying to find some commonality of process or symptoms. check bugs Bug 131906 Bug 162290 Bug 147822 Bug 162609 Bug 151751 maybe bug 160779 confirming bug and taking
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: ktrina → gbush
Comment 6•22 years ago
|
||
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: major → critical
Comment 8•21 years ago
|
||
Mozilla 1.5 forgets further occasionally all settings incluiding Mail & Newsgroups Accounts. Bookmarks these meal were not deleted. A connection with a hardware (Voltage?) error is possible. To restore the mails, shift the associated directorys to another place, recreate the accounts and back-shift the directorys. I think, the algorithm to write the actual browser settings must have a fundamental error, which leads to corrupt files, if the recording procedure is not up to end executed. If the browser notices later this, he probably overwrites simply the files with a standard design. I think, he might never do this without asking the user. This critical error exists apparently since Netscape 4.x
No response, old bug/version ... like Bug 209301. IMHO this could be resolved as dupe of Bug 193638.
Comment 10•20 years ago
|
||
Old version, no further response. Not useful anymore. I resolve it as dupe. Feel free to reopen it if you disagree. *** This bug has been marked as a duplicate of 193638 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•