183464 - mozilla1.2 and 1.2.1 go zombie when following the build in New Themes link

Status: RESOLVED DUPLICATE of bug 144027

(SeaMonkey :: General, defect)

Description

[martin smidt]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530

small history, 
used moz1.0 all ok, 
uninstalled 1.0, installed 1.2, follow themes link, install skins, all ok
uninstalled 1.2, installed 1.2.1, follow Get New Themes, click on deskmod or
mozdev.org, no reaction. close mozilla, mozilla appears gone, but taskmanager
shows mozilla still running -> zombie
uninstall 1.2.1, delete mozilla dir, install 1.2, same problem
uninstall 1.2, delete mozilla dir, install 1.2.1, same problem
uninstall 1.2, install 1.0, no problem

Reproducible: Always

Steps to Reproduce:
1. see details above
2. 
3.

Actual Results:  
see details

Expected Results:  
release a version which works properly

Comment 1

[Matthias Versen [:Matti]]

Reporter: Have you installed this Theme or is the installation itself broken ?

Comment 2

[martin smidt]

i never came to the Theses site, so never came to install a Theme 
1st i thought the theme site must be dead, i could still browse to other sites
then i closed mozilla, and tried to start it again, but nothing came up, so
i checked with taskmanager and saw that mozilla was still running although it
had no windows. remined me of the netscape 4.7 zombies - problem appears identical.
the theme is thus not the problem ! it is mozilla going zombie ! and mozilla
kept going zombie every time after i killed mozilla, restarted and went to
themes site.
i returned to mozilla 1.0 and which never showed any of this zombie stuff
ps. i never rebooted inbetween all this

Comment 3

[R.K.Aa.]

zombie processes also mentioned by some users in bug 183161.

Martin:
Can you please try quit mozilla, and also quickstart if you use that.
Make sure mozilla processes are running - kill what's left.
Then delete the file XUL.mfl in your profile directory, and restart mozilla.
(XUL.mfl will be re-created on starup of missing)

Does that change anything?

Comment 4

[R.K.Aa.]

i meant "make sure NO mozilla processes are running.."

Comment 5

[martin smidt]

i repeated the whole thing again, 
problem remains identical !
never used quickstart, so only kill mozilla.exe everytime
removing XUL.mfl made no difference

interesting is that after every new installation, mozilla starts with mail and
Classic theme. 

ok .. new install 1.2.1, Get new Themes, click on link, no reaction
copy link location to address bar and it reads the page correctly
install theme orbit3+1
change to theme
close mozilla, taskman shows mozilla.exe still running, kill mozilla.exe
start mozilla, opens with mail ! and cannot open browser !!
kill, start, same -> only mail, no browser (getting **** here)
uninstall 1.2.1, install 1.0
opens with classic theme, install new theme via links, all works fine
---
on another pc, that has never seen mozilla, also winxp.pro
install moz1.2.1
opens with modern theme (surprise)
Get New Themes, follow link (works fine), install Orbit3+1, select orbit3+1
close, start mozilla, all fine, no problem here at all
(regained some confidence in mozilla)
---
to me it looks like new installations inhererit an excisting problem (to which
mozilla 1.0 appears immune)
---

Comment 6

[R.K.Aa.]

the Installation Notes mention that mozilla should be installed to an empty
directory. When you uninstall, please also make sure that at least the remaining
"chrome" and "components" directories are deleted, before installing a new build.

Please try that approach if you haven't already.

If the problem still persists then: Created a new user-profile (profilemanager)
and see if the problem also happens when using that profile.

Comment 7

[martin smidt]

installing in an empty dir had no effect, problem remains.
i will try the the profile idea later

Comment 8

[Torben]

Bet this is something in your old profile, try to delete the file chrome.rdf.

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