66470 - Browser hangs on start if configured theme isn't present

Status: VERIFIED DUPLICATE of bug 53670

(SeaMonkey :: Themes, defect)

Description

[Dave]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.15-4mdk i686; en-US; m18) Gecko/20010118
BuildID:    2001011800

If I upgrade to a newer nightly while using a theme other than one of the
defaults, the browser hangs when I try to start the new build because it can't
find the theme that's configured in ~/.mozilla/.../chrome/user-skins.rdf

Reproducible: Always
Steps to Reproduce:
1.) Have a nightly installed.
2.) Download new skin (http://x.themes.org has plenty).
3.) Set new theme as default.
4.) Download new nightly
5.) rm -rf package (or whatever your mozilla binary directory is called... where
the new theme was installed).
6.) tar zxf <moz-tarball>
7.) Run new build with old ~/.mozilla directory.
8.) Browser hangs after registering plugins.

Actual Results:  Browser doesn't load... ever.

Expected Results:  Browser window should appear

I got around this by renaming my ~/.mozilla/.../chrome/user-skins.rdf file and
restarting the browser, at which point it loaded with the classic theme.

Comment 1

[Dave]

BTW, I think this bug happens no matter what theme you're using (other than the
ones that come with the builds) but, for the record, I was using GreyModern (off
x.themes.org) when this happened.

Comment 2

[Matthias Versen [:Matti]]

Dupe of 53670

(New build won't start if 3rd party theme is used in old build)

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

Comment 3

[Stephen Walker]

vrfy dup