Closed Bug 50668 Opened 25 years ago Closed 25 years ago

Installed mozilla will NOT launch - hangs

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: benson.guthrie, Assigned: hyatt)

References

(
URL
)

Details

(Keywords: smoketest, Whiteboard: [dogfood+])

in reference to: http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32-installer.exe 29-Aug-2000 06:33 6.6M I downloaded , no problem. executed the installer, no apparent problems. I chose to delete the previous instalation, custom: no chatzilla, no mail & news profile manager automatically launched, I chose a profile. Mozilla hangs on the rectangle window with the fire breathing gecko. I've killed the process with task manager & tried relaunching the ap, same problem. I rebooted, downloaded a second time, installed again, same results
Severity: major → critical
Keywords: smoketest
Tinderbox shows no horkage. Can anyone confirm?
yep. just hangs there. Changing the component to Browser-General.
Assignee: ssu → asa
Component: Installer → Browser-General
QA Contact: gemal → doronr
ssu, this is only happening with the installered version of the binary... if you use a zip file of dist, things work great. I'll try to compare the directories and see if i can spot glaring ommissions in jars/dlls
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 50671 has been marked as a duplicate of this bug. ***
i bet a chrome file changed and the .mn files are out of date. help me find out what changed, dprice.
Assignee: asa → dprice
the installer is not generating the all-foo.rdf files or the user-foo.rdf files in chrome/ and the installed-chrome.txt is not going away after first 'launch'. The zip is working fine, and moving it's .rdf's to the installer's directory made the installer work fine.
adding Dan to the CC: list.
installer worked fine on linux build 2000-08-29-08-m18
This also occurs on Commercial Win32 /2000-08-29-08-M18/ build
Whiteboard: [dogfood+]
Summary: Mozilla will NOT launch - hangs → Application will NOT launch - hangs
installed-chrome.txt isn't there? That's not right. Was it there on Monday? If it was there on Monday, then I don't think it is the fault of jar packaging. The only changes we made on Monday were to make-jars.pl and correcting some jar.mn files. They don't touch that file. If it wasn't there on Monday, then I'd point the finger of blame at the installer changes that warren did on Friday night. I'm not that familiar with it, but I'm willing to lend a hand.
Sorry, it is there, and is not going away after first launch. If I understand correctly, it should go away, and be replaced with the user-*.rdf and all-*.rdf files, which is not happening.
installed-chrome.txt not going away means the failure/hang happens before the chrome registry wakes up and does its stuff. This might be very useful in narrowing down where the error is. Hyatt: when/where is the chrome registry stuff kicked off?
Mark blocker: per kerz, there is no workaround so we don't have any builds after Friday (8/25) that we can test AIM in.
Severity: critical → blocker
installer in summary
Summary: Application will NOT launch - hangs → Installed mozilla will NOT launch - hangs
Damn. Mine.
Assignee: dprice → hyatt
Fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified with 082915 on windows.
Status: RESOLVED → VERIFIED
*** Bug 50680 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.