72267 - need ability to detect invalid chromes in profile

Status: RESOLVED INCOMPLETE

(Toolkit :: Startup and Profile System, defect)

Description

[Morten Nilsen]

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

[Keyser Sose]

Reporter does it still crash with the latest nightlies?

Comment 2

[Morten Nilsen]

I confirm. still crashes with latest nightly (tested a few minutes before this
report)

Comment 3

[Conrad Carlen (not reading bugmail)]

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. 
 
 

Comment 4

[Morten Nilsen]

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.

Comment 5

[Morten Nilsen]

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 [e-mail]
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

Comment 6

[Morten Nilsen]

Attachment: file causing bug (In my case)

Comment 7

[Morten Nilsen]

This is the file causing the problem. I managed to determine this as 0.8.1 was
released.

Comment 8

[Conrad Carlen (not reading bugmail)]

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.

Comment 9

[Keyser Sose]

Marking NEW because it has good info in it.

Comment 10

[Morten Nilsen]

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

[Paul Chen]

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-

Comment 12

[Ben Goodger (use ben at mozilla dot org for email)]

Mass move skinability bugs to [e-mail], helpwanted. 

Comment 13

[Morten Nilsen]

changing comment to reflect where this bug went

Comment 14

[Conrad Carlen (not reading bugmail)]

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.

Comment 15

[Morten Nilsen]

*** Bug 115195 has been marked as a duplicate of this bug. ***

Comment 16

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"

Comment 17

[Robert Kaiser]

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.