Closed
Bug 174290
Opened 22 years ago
Closed 22 years ago
Crash while installing skins, mozilla refuses to start anymore
Categories
(Core Graveyard :: Skinability, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: chswing, Assigned: bugs)
Details
(Keywords: crash, stackwanted)
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705) Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.1/mozilla-win32-1.1-installer.exe I was running Mozilla 1.1, and while doing so, was running multiple skin installs. Mozilla locked and crashed, and refuses to start anymore. At bootup, it loads the agent, but Navigator won't start. If I kill the agent and attempt to start Mozilla again, it hangs at the splash screen. Reproducible: Didn't try Steps to Reproduce: 1. Install multiple skins simultaneously. 2. 3. Actual Results: Mozilla crashes. Afterword, it refuses to start. Expected Results: Installed all of the skins. I was in the Default theme, and the Netscape QF agent was TB12512787Y.
Reporter | ||
Comment 1•22 years ago
|
||
Uninstall/Reinstall doesn't help. Time to go clear directories and hack through the registry with a sickle.
Updated•22 years ago
|
Keywords: crash,
stackwanted
Whiteboard: TB12512787Y
Comment 2•22 years ago
|
||
Stephen, can you retreive Talkback data please TB12512787Y ?
the incident ID is older than 30 days, therefore it doesn't exist in the talkback database (we only archive a month's worth, sorry)
Whiteboard: TB12512787Y
Comment 4•22 years ago
|
||
Christopher, do you still crash using latest nightly build ? http://ftp.mozilla.org/pub/mozilla/nightly/latest If so, please post a new Talkback ID for such a crash.
Comment 5•22 years ago
|
||
no response from reporter for >30 days. resolving WORKSFORME. reporter: if you can reproduce this with a recent build of mozilla, please reopen this bug and give details. thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•