67035 - Crash on reading a ?broken? profile

Status: VERIFIED DUPLICATE of bug 53670

(Core :: Preferences: Backend, defect)

Description

[Michal 'hramrach' Suchanek]

I was unable to run Mozilla 20010125, 0.7, 0.6 on Linux (Red Hat 6). It
registered plugins and hanged.
I discovered that when I delete the chrome subdirectory of my profile, it's
possible to run Mozilla without problems.
When I tried to reuse parts of my profile, Mozilla even crashed.

To reproduce:
1) Unpack the Default User profile (I will create an attachment) and put it into
.mozilla directory.
2) run mozilla -ProfileManager
3) create the profile Deafult User (this normally works and *should* work to
allow sharing profiles on network drives between computers)
4) start mozilla with the newly created profile

Result: Mozilla crashes.

Expected: Enjoy browsing with my precious bookmarks passwords, etc :)

Comment 1

[Michal 'hramrach' Suchanek]

Attachment: prat of my profile that coaused Mozilla to crash (.tar.gz archive)

Comment 2

[Fabian Guisset]

When you first installed Mozilla, did you have another theme than the default?
If yes, you are maybe running into bug 53670 "New build won't start if third
party theme is used in old build".

Comment 3

[Michal 'hramrach' Suchanek]

It may be the case but it was the same build, it just didn't contain the theme.
I have Mozilla on NFS. That is very slow. I wrote a scipt to copy it into a
temporary directory and run it from there. I installed a theme which went into
the temporary directory and later runned a copy (probably) without the theme.

Comment 4

[Michal 'hramrach' Suchanek]

Yes, it's that bug. It just should name "Mozilla won't start if selected theme
isn't available".

Comment 5

[Keyser Sose]

*** This bug has been marked as a duplicate of 53670 ***

Comment 6

[sairuh (rarely reading bugmail)]

mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.