Closed
Bug 72267
Opened 23 years ago
Closed 12 years ago
need ability to detect invalid chromes in profile
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
INCOMPLETE
Future
People
(Reporter: Morten, Unassigned)
References
Details
(Keywords: crash, helpwanted, Whiteboard: low frequency)
Attachments
(1 file)
1.23 KB,
text/plain
|
Details |
I have a Mozilla 0.8 installed, and when I install the nightly build, selecting my old profile crashes the nighly build. I've had this problem previosly when 0.8 was released.. back then I found a workaround; creating a blank profile, creating all mail-accounts anew, quit mozilla, and copy the mail-files into the new profile.
Comment 1•23 years ago
|
||
Reporter does it still crash with the latest nightlies?
Severity: blocker → critical
Keywords: crash
Reporter | ||
Comment 2•23 years ago
|
||
I confirm. still crashes with latest nightly (tested a few minutes before this report)
Comment 3•23 years ago
|
||
Morten, your workaround: "creating a blank profile, creating all mail-accounts anew, quit mozilla, and copy the mail-files into the new profile" Does this workaround still work? If so, and you didn't wipe the whole folder which contains "Users50" and "registry.dat", that eliminates some possibilities - at least the registry.
Reporter | ||
Comment 4•23 years ago
|
||
I didn't delete anything, no... I'm trying to copy one by one file to find it now... the files that don't cause the problem; URL.tbl search.rdf secmod.db prefs.js panels.rdf panacea.dat mimeTypes.rdf localstore.rdf key3.db history.mab history.dat cookies.txt cert7.db bookmarks.html abook.mab 82355225.w 82355189.s Cache folder en-us folder ImapMail folder Mail folder News Folder --------------- The folder Chrome causes it. renaming that to chrome_ lets mozilla start again. If wanted, I can create an attachment of that folder.
Reporter | ||
Comment 5•23 years ago
|
||
More info: when mozilla was started with chrome renamed to chrome_, it created a new chrome. and when I swapped the two, mozilla still started. This might give some clue to the precise location of the bug. The process I used now rendered the mailboxes unusable. no expand button, and the selecting the account header, displayed this text in the mail list frame: Mozilla Mail fo Morten@nilsen.com Email Read my Email messages Compose a new message Accounts View settings for his account Create a new account Advanced Features Search my messages Create message filters
Reporter | ||
Comment 6•23 years ago
|
||
Reporter | ||
Comment 7•23 years ago
|
||
This is the file causing the problem. I managed to determine this as 0.8.1 was released.
Comment 8•23 years ago
|
||
Thanks for doing the detective work. What is the skin - native.windows? Since that's the problem, it's not a profile mgr back-end problem. Changing component.
Assignee: ccarlen → ben
Component: Profile Manager BackEnd → Skinability
QA Contact: gbush → blakeross
Comment 9•23 years ago
|
||
Marking NEW because it has good info in it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 10•23 years ago
|
||
I discovered the actual reason, but forgot to enter it into bugzilla... I chose not to place the skins files in the profile folder... maybe there should be some extra warning or auto-detection of missing skin-files?
Comment 11•23 years ago
|
||
nav triage team: The work to detect an invalid chrome directory in the profile certainly won't get done my beta. Marking future and nsbeta1-
Keywords: nsbeta1-
Target Milestone: --- → Future
Comment 12•23 years ago
|
||
Mass move skinability bugs to nobody@mozilla.org, helpwanted.
Assignee: ben → nobody
Keywords: helpwanted
Reporter | ||
Comment 13•23 years ago
|
||
changing comment to reflect where this bug went
Summary: crash upon using mozilla 0.8 profile in nightly build as of Mar 17th 2001 01:20:21 → need ability to detect invalid chromes in profile
Comment 14•23 years ago
|
||
This comment is from bug 115195 which is nearly a dup of this one. It does describe this variation on the problem which is useful: ------------- When a new install of mozilla is started, if you have installed a theme/skin, and the files where placed in the old mozilla binary folder (which is now gone) the startup will fail, silently, last time I was able to check. Therefor I think the profile manager backend, (or another component) should ignore chromes that no longer exist on disk, possibly warning the user about it. ------------- CC'ing hyatt because I think it's a chrome registry problem.
Reporter | ||
Comment 15•23 years ago
|
||
*** Bug 115195 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•16 years ago
|
Product: Core → Core Graveyard
Updated•15 years ago
|
Component: Skinability → Startup and Profile System
Product: Core Graveyard → Toolkit
QA Contact: skinability → startup
Comment 17•12 years ago
|
||
This doesn't have info about anything on new code, if it still happens, please file a new bug with an actual crash signature or reopen this one and update it with current info.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•